> On 3 Aug 2016, at 10:29, teor <[email protected]> wrote: > > Clients on 0.2.7.6 and earlier still use the IPv4 DirPort. > (Tor Browser is still 0.2.7.6, and apps in general may take some time to > upgrade.) > > Authorities on0.2.7.6 and earlier will only assign the HSDir flag to relays > with an IPv4 DirPort. > (Authorities may take some time to upgrade, because running different > versions increases authority diversity.)
For the record, even though the man page entry for HidServDirectoryV2 says the
DirPort is not required to be a HSDir, authorities on 0.2.7 and earlier still
check for it before assigning the HSDir flag.
Authorities on 0.2.8 and later behave in a way that's consistent with
HidServDirectoryV2, assigning the HSDir flag to any relay that wants to be a
HSDir, and either supports being a directory cache, or has a DirPort.
HidServDirectoryV2 0|1
When this option is set, Tor accepts and serves v2 hidden service
descriptors. Setting DirPort is not required for this, because
clients connect via the ORPort by default. (Default: 1)
> Fallback directory mirrors must have a DirPort, and we'd only think about
> changing that when:
> * all recommended relay versions are 0.2.8 and later, and
> * relays no longer fetch documents using the DirPort (so maybe never).
>
> All relays running any Tor version will continue to use the IPv4 DirPort to
> fetch consensuses from other relays.
>
> So we haven't obsoleted the IPv4 DirPort yet. We've just made sure that
> clients fetch directory documents over an encrypted channel.
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
