[tor-relays] Bridge relays should upgrade to use the new bridge authority
teor at riseup.net
Thu Jul 19 04:08:05 UTC 2018
> On 19 Jul 2018, at 10:18, nusenu <nusenu-lists at riseup.net> wrote:
>>> Roger Dingledine:
>>>> If you run a bridge relay, please upgrade -- so your bridge address can
>>>> resume being given out to censored users, and so your stats can resume
>>>> being included in the metrics pages.
>>>> We just put out new releases (0.2.9.16, 0.3.2.11, 0.3.3.9, 0.3.4.5-rc)
>>>> that retire the old bridge authority and start using a new one. The new
>>>> bridge authority is "Serge", and it is operated by George from the Tor
>>>> BSD Diversity project:
>>>> If for whatever reason you can't upgrade yet, you can also manually
>>>> switch to advertising your bridge descriptor to the new bridge authority
>>>> by using this torrc line:
>>>> AlternateBridgeAuthority Serge orport=9001 bridge 22.214.171.124:9030 BA44 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533
>>> I'd expect such email to be signed - yes, even if people can fetch that
>>> data from a signed release.
>> Please submit a patch to ReleasingTor.md.
> Since Roger's email wasn't the release announcement that email is
> not in scope of ReleasingTor.md?
If we want the release manager to follow a process when notifying relay
operators about a release, the best place to document that process is
Please add another paragraph about emailing affected operators after the
existing "Mail the release blurb and ChangeLog” paragraph at:
For relay and bridge operators, the appropriate list is:
tor-relays at lists.torproject.org
For directory authority operators, the appropriate list is:
dir-auth at lists.torproject.org
Then you can replace “mail” with "signed mail” where appropriate.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: Message signed with OpenPGP
More information about the tor-relays