Hi folks!
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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131:9030 BA44 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533
Thanks! --Roger
you probably want to reach out to package maintainer that didn't update yet (like the ubuntu snap) - if you didn't do so yet
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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131: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.
On 19 Jul 2018, at 06:40, nusenu nusenu-lists@riseup.net wrote:
Signed PGP part you probably want to reach out to package maintainer that didn't update yet (like the ubuntu snap) - if you didn't do so yet
Emailing package maintainers is part of our existing process: https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n171
If the maintainer is not on the list, please submit a patch to ReleasingTor.md, or ask them to join tor-packagers@lists.torproject.org.
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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131: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.
T
you probably want to reach out to package maintainer that didn't update yet (like the ubuntu snap) - if you didn't do so yet
Emailing package maintainers is part of our existing process: https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n171
Chad, do you want to be on the list linked above?
If the maintainer is not on the list, please submit a patch to ReleasingTor.md, or ask them to join tor-packagers@lists.torproject.org.
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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131: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?
On 19 Jul 2018, at 10:18, nusenu nusenu-lists@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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131: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 ReleasingTor.md.
Please add another paragraph about emailing affected operators after the existing "Mail the release blurb and ChangeLog” paragraph at: https://gitweb.torproject.org/tor.git/tree/doc/HACKING/ReleasingTor.md#n210
For relay and bridge operators, the appropriate list is: tor-relays@lists.torproject.org
For directory authority operators, the appropriate list is: dir-auth@lists.torproject.org
Then you can replace “mail” with "signed mail” where appropriate.
T
On Wed, Jul 18, 2018 at 08:40:00PM +0000, nusenu wrote:
you probably want to reach out to package maintainer that didn't update yet (like the ubuntu snap) - if you didn't do so yet
Right, those people should be on the tor-packagers list if they want to hear about it.
There is also a separate list of people that we mail personally, like the Debian maintainer, because we're the ones who care most about having the new update happen so it's polite of us to do the extra work. We could add more people to that list.
AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131: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.
I actually thought about signing it but then I realized that mailman mangles messages to the point that my signatures usually end up bad (yours do too :/ ), so it didn't seem worth fighting with that one.
--Roger
Roger Dingledine:
I'd expect such email to be signed - yes, even if people can fetch that data from a signed release.
I actually thought about signing it but then I realized that mailman mangles messages to the point that my signatures usually end up bad (yours do too :/ ), so it didn't seem worth fighting with that one.
The GPG signature of my emails doesn't appear to be broken on the ML from here. I get "Part of the message signed Good signature from nusenu nusenu-lists@riseup.net" due to the added footer I assume. Could you elaborate what you mean with "bad"?
- does it affect all GPG signed email on this list? - does it affect only my emails? - does it affect all my email or only some? - which once are affected (ideally identified by message-id)
thanks
On 2018-07-19 22:13, nusenu wrote:
I actually thought about signing it but then I realized that mailman mangles messages to the point that my signatures usually end up bad (yours do too :/ ), so it didn't seem worth fighting with that one.
The GPG signature of my emails doesn't appear to be broken on the ML from here. I get
"Part of the message signed Good signature from nusenu nusenu-lists@riseup.net"
This may be of interest:
https://very.loosely.org/itz-blog/the-problem-with-gpg-signatures.html
Hello tor-relay folks,
I'm confused--not a new thing but likely that this group can help this time. After Roger's email below, I updated my Tor bridges to current. Strangely, NYX reports that they are the "un-recommended" release. When I check with tor --version, I get a reply that is the current software. Additionally, my bridges don't display when I enter their hashed footprint into Tor Metrix. They always have before.
What goes on?
Arisbe
On 7/14/2018 1:33 PM, Roger Dingledine wrote:
Hi folks!
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: https://lists.torproject.org/pipermail/tor-announce/2018-July/000162.html
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 66.111.2.131:9030 BA44 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533
Thanks! --Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
When I check with tor --version, I get a reply that is the current software
please paste the output of that command
arisbe:
Two of my bridges (not all) show the same response:
hamlet@v3460:~$ tor --version Tor version 0.3.3.9 (git-ca1a436fa8e53a32). hamlet@v3460:~$
Thanks for looking at this discrepancy.
is NYX showing the same version? if not: did you restart tor after upgrading?
arisbe:
On 7/22/2018 11:59 PM, nusenu wrote:
arisbe:
Two of my bridges (not all) show the same response:
hamlet@v3460:~$ tor --version Tor version 0.3.3.9 (git-ca1a436fa8e53a32). hamlet@v3460:~$
Thanks for looking at this discrepancy.
is NYX showing the same version?
nyx shows the old Tor that was upgraded Tor 0.3.1.9if not: did you restart tor after upgrading?
When I saw the version discrepancy and also noticed no metrics data, Irestarted Tor and then went further and rebooted linux. Everything stayed the same. I see users on both bridges and also see Bifroest communicating with both.
if nyx still says you run 0.3.1.9 and NOT 0.3.3.9 - even after a restart than you might want to look into your tor installations and PATHs
On 24 Jul 2018, at 12:20, arisbe arisbe@cni.net wrote:
The other issue is why these two bridges don't show up on Tor Metrics.
Hamlet and Othello
Tor metrics just published an explanation of how they get their statistics: https://metrics.torproject.org/reproducible-metrics.html
Perhaps your bridges don't report statistics, or they are excluded by one of the other checks.
T
tor-relays@lists.torproject.org
-
arisbe -
Ian Zimmerman -
nusenu -
Roger Dingledine -
teor