Opened 4 years ago

Last modified 3 years ago

#19853 new defect

ServerDNSAllowNonRFC953Hostnames affects clients, and AllowNonRFC953Hostnames affects servers

Reported by: teor Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Minor Keywords: easy, doc tor-client dns
Cc: Actual Points:
Parent ID: Points: 0.1
Reviewer: Sponsor:


It looks like the code and man page entry for ServerDNSAllowNonRFC953Hostnames was copied straight from AllowNonRFC953Hostnames, which is the equivalent client option.

I think this is ok as-is, because even though both options affect both client and server, tor instances typically only run as clients or servers, not both.

However, the manual page entries could be updated to clarify that the options are synonyms, and affect both clients and exits.

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:2 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:3 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 3 years ago by nickm

Keywords: tor-client dns added
Note: See TracTickets for help on using tickets.