Update DirAuthority man entry for client begindir, no IPv6 DirPort

Tor's DirAuthority entry says: Tor will contact the authority at address:port (the DirPort) to download directory documents. If an IPv6 address is supplied, Tor will also download directory documents at the IPv6 address on the DirPort.

But no Tor instance uses the IPv6 DirPort:

• clients (>= 0.2.8) use the IPv4 ORPort,
• clients (< 0.2.8) and relays use the IPv4 DirPort.

changed milestone to %Tor: 0.3.2.x-final

added component::core tor/tor easy milestone::Tor: 0.3.2.x-final owner::nickm parent::18892 points::0.1 priority::medium resolution::fixed severity::normal status::closed tor-doc type::defect labels

Agreed!

For posterity though, the version cutoff for where clients started using the ORPort, i.e. for when we deployed the begindir design, is 0.2.0.22-rc:

  o Major features:
    - Enable encrypted directory connections by default for non-relays,
      so censor tools that block Tor directory connections based on their
      plaintext patterns will no longer work. This means Tor works in
      certain censored countries by default again.

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

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

Trac:
Keywords: easy doc deleted, tor-03-unspecified-201612, doc, easy added
Milestone: Tor: 0.3.??? to Tor: unspecified

Trac:
Username: kleft
Parent: N/A to #18892 (moved)
Cc: N/A to kleft

According to roadmaps/Tor/IPv6, 0.2.8-alpha-dev and newer are able to connect to DirAuthorities and FallbackDirs via v6, can anyone confirm that this is correct, implemented and working?

Trac:
Username: kleft

Replying to kleft:

According to roadmaps/Tor/IPv6, 0.2.8-alpha-dev and newer are able to connect to DirAuthorities and FallbackDirs via v6, can anyone confirm that this is correct, implemented and working?

Yes, it works, and it requires the ClientUseIPv6 and ClientPreferIPv6 options to be set on the client, as documented in the man page.

(This isn't really the place to discuss this question, if Tor doesn't behave how you expect, please open another ticket.)

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: doc deleted, tor-doc added
Milestone: Tor: unspecified to Tor: 0.3.2.x-final

Trac:
Status: new to accepted
Owner: N/A to nickm

Trivial patch in branch bug21052 in my public repository.

Trac:
Status: accepted to needs_review

The IPv6 address always comes with an ORPort, which is potentially different to the IPv4 ORPort.

So let's revise with:

• s/IPv6 address is supplied/IPv6 ORPort is supplied/
• s/IPv6 address on the ORPort/IPv6 ORPort/ then merge.

Trac:
Status: needs_review to needs_revision

Fixed and merged!

Trac:
Resolution: N/A to fixed
Status: needs_revision to closed

closed

changed time estimate to 48m

moved to tpo/core/tor#20152 (closed)