Opened 6 years ago

Closed 6 years ago

#9061 closed defect (wontfix)

Warning about low DirPort or OrPort wrong

Reported by: hsn Owned by: ioerror
Priority: Medium Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

if I use different ports to advertise Dir/Or port and different ports to listen. Tor checks advertised ports, not real ones and issues warning

[warn] You have set AccountingMax to use hibernation. You have also chosen a low DirPort or OrPort. This combination can make Tor stop working when it tries to re-attach the port after a period of hibernation. Please choose a different port or turn off hibernation unless you know this combination will work on your platform.

configuration
DirPort 80
DirListenAddress 216.17.1.3:8080

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by rransom

Component: TorouterTor

comment:2 Changed 6 years ago by nickm

Keywords: 024-backport added
Milestone: Tor: 0.2.3.x-finalTor: 0.2.5.x-final

Good catch! Putting this in 0.2.5 with a possibility of a backport to 0.2.4 if the fix is simple and clean. This is probably not suitable for 0.2.3 -- we're only backporting really serious bugfixes to that one.

comment:3 Changed 6 years ago by nickm

Actually ... does 0.2.4 have this bug? It looks just like #7285, which is fixed now.

comment:4 Changed 6 years ago by nickm

Status: newneeds_information

comment:5 Changed 6 years ago by hsn

version is Tor 0.2.3.25

comment:6 Changed 6 years ago by nickm

Keywords: 024-backport removed
Milestone: Tor: 0.2.5.x-finalTor: 0.2.3.x-final
Resolution: wontfix
Status: needs_informationclosed

Okay. If this is fixed in 0.2.4, I am going to close it as "won't backport" -- 0.2.3 is the most-stable release at this point, and we should only be backporting fixes for critical issues.

Please reopen if this bug also exists in 0.2.4 or later.

Note: See TracTickets for help on using tickets.