-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
FYI: I just sent out the email bellow to ~160 relay operators - I hope this results in some actual improvements.
It is a bit disappointing to see even torservers.net, DFRI, icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list.
The recipient list is based on the following output (limited to relays faster than 999KB/s):
grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de)
Hello,
you are receiving this email because you are using an outdated tor version on your tor relay. (your email address was taken from your relay's contact info field)
Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a security issue that makes de-anonymization attacks easier [2] - please update to Tor v0.2.4.23 or v0.2.5.6.
To find out your current version run the following command on your relay: tor --version
If you are using Linux: Package managers can be used to automatically update Tor without requiring manual admin intervention.
It is recommended to use the official APT/YUM repos from torproject.org to get timely updates: APT: https://www.torproject.org/docs/debian.html.en YUM: https://www.torproject.org/docs/rpms.html.en
thanks for running a relay and making the tor network safer!
[1] https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html
[2]
https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html
Let it never be said that public shaming doesn't work, I'll update our exits tonight! -Jason
On 08/17/2014 10:45 AM, Nusenu wrote:
FYI: I just sent out the email bellow to ~160 relay operators - I hope this results in some actual improvements.
It is a bit disappointing to see even torservers.net, DFRI, icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list.
The recipient list is based on the following output (limited to relays faster than 999KB/s):
grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de)
Hello,
you are receiving this email because you are using an outdated tor version on your tor relay. (your email address was taken from your relay's contact info field)
Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a security issue that makes de-anonymization attacks easier [2] - please update to Tor v0.2.4.23 or v0.2.5.6.
To find out your current version run the following command on your relay: tor --version
If you are using Linux: Package managers can be used to automatically update Tor without requiring manual admin intervention.
It is recommended to use the official APT/YUM repos from torproject.org to get timely updates: APT: https://www.torproject.org/docs/debian.html.en YUM: https://www.torproject.org/docs/rpms.html.en
thanks for running a relay and making the tor network safer!
[1] https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html
[2]
https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org repo's yet. I'll be waiting for them first. -Jason
On 08/18/2014 02:55 AM, jason@icetor.is wrote:
Let it never be said that public shaming doesn't work, I'll update our exits tonight! -Jason
On 08/17/2014 10:45 AM, Nusenu wrote:
FYI: I just sent out the email bellow to ~160 relay operators - I hope this results in some actual improvements.
It is a bit disappointing to see even torservers.net, DFRI, icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list.
The recipient list is based on the following output (limited to relays faster than 999KB/s):
grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de)
Hello,
you are receiving this email because you are using an outdated tor version on your tor relay. (your email address was taken from your relay's contact info field)
Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a security issue that makes de-anonymization attacks easier [2]
- please update to Tor v0.2.4.23 or v0.2.5.6.
To find out your current version run the following command on your relay: tor --version
If you are using Linux: Package managers can be used to automatically update Tor without requiring manual admin intervention.
It is recommended to use the official APT/YUM repos from torproject.org to get timely updates: APT: https://www.torproject.org/docs/debian.html.en YUM: https://www.torproject.org/docs/rpms.html.en
thanks for running a relay and making the tor network safer!
[1] https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html
[2]
https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html
_______________________________________________
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
0.2.4.23 has been on the repo for awhile now.
--- GPG/PGP Fingerprint E129 722B A512 105C E8BE 4705 8046 EA48 2C82 1339 https://arlen.io/key On Aug 17, 2014 11:40 PM, jason@icetor.is wrote:
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org repo's yet. I'll be waiting for them first. -Jason
On 08/18/2014 02:55 AM, jason@icetor.is wrote:
Let it never be said that public shaming doesn't work, I'll update our exits tonight! -Jason
On 08/17/2014 10:45 AM, Nusenu wrote:
FYI: I just sent out the email bellow to ~160 relay operators - I hope this results in some actual improvements.
It is a bit disappointing to see even torservers.net, DFRI, icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list.
The recipient list is based on the following output (limited to relays faster than 999KB/s):
grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de)
Hello,
you are receiving this email because you are using an outdated tor version on your tor relay. (your email address was taken from your relay's contact info field)
Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a security issue that makes de-anonymization attacks easier [2]
- please update to Tor v0.2.4.23 or v0.2.5.6.
To find out your current version run the following command on your relay: tor --version
If you are using Linux: Package managers can be used to automatically update Tor without requiring manual admin intervention.
It is recommended to use the official APT/YUM repos from torproject.org to get timely updates: APT: https://www.torproject.org/docs/debian.html.en YUM: https://www.torproject.org/docs/rpms.html.en
thanks for running a relay and making the tor network safer!
[1]
https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html
[2]
https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
yep you're correct, I should have taken note of the version numbers better. All exits have been updated now. -J
On 08/18/2014 03:48 AM, JT Allison wrote:
0.2.4.23 has been on the repo for awhile now.
GPG/PGP Fingerprint E129 722B A512 105C E8BE 4705 8046 EA48 2C82 1339 https://arlen.io/key
On Aug 17, 2014 11:40 PM, <jason@icetor.is mailto:jason@icetor.is> wrote:
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org <http://deb.torproject.org> repo's yet. I'll be waiting for them first. -Jason On 08/18/2014 02:55 AM, jason@icetor.is <mailto:jason@icetor.is> wrote: > Let it never be said that public shaming doesn't work, I'll update > our exits tonight! -Jason > > On 08/17/2014 10:45 AM, Nusenu wrote: >> FYI: I just sent out the email bellow to ~160 relay operators - I >> hope this results in some actual improvements. >> >> It is a bit disappointing to see even torservers.net <http://torservers.net>, DFRI, >> icetor, Frenn vun der Enn, Calyx, Cymru in the recipients list. >> >> The recipient list is based on the following output (limited to >> relays faster than 999KB/s): >> >> grep -v 0.2.5.6 Tor_query_EXPORT.csv |grep -v 0.2.4.23|grep -v >> 0.2.6.0|head -n 344 (csv is from torstatus.blutmagie.de <http://torstatus.blutmagie.de>) >> >>> Hello, >> >>> you are receiving this email because you are using an outdated >>> tor version on your tor relay. (your email address was taken >>> from your relay's contact info field) >> >>> Tor v0.2.4.23 has been released on 2014-07-28 [1] to address a >>> security issue that makes de-anonymization attacks easier [2] >>> - please update to Tor v0.2.4.23 or v0.2.5.6. >> >>> To find out your current version run the following command on >>> your relay: tor --version >> >>> If you are using Linux: Package managers can be used to >>> automatically update Tor without requiring manual admin >>> intervention. >> >> >>> It is recommended to use the official APT/YUM repos from >>> torproject.org <http://torproject.org> to get timely updates: APT: >>> https://www.torproject.org/docs/debian.html.en YUM: >>> https://www.torproject.org/docs/rpms.html.en >> >> >>> thanks for running a relay and making the tor network safer! >> >> >>> [1] >>> https://lists.torproject.org/pipermail/tor-announce/2014-July/000093.html >> >> >> >>> [2] >>> https://lists.torproject.org/pipermail/tor-announce/2014-July/000094.html >> >> >> >>> _______________________________________________ >> tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> > > _______________________________________________ tor-relays mailing > list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
jason@icetor.is:
yep you're correct, I should have taken note of the version numbers better. All exits have been updated now.
is atlas wrong/not up to date yet about loki2 having an uptime of 60 days and still running tor v0.2.4.22?
https://atlas.torproject.org/#details/5CECA69D0D91B5B38376B98B761BE18938297E...
I'm not sure why atlas hasn't updated yet but currently loki1 is running 2.4.23. As well as loki2 and loki3. -Jason
On 08/18/2014 07:02 PM, Nusenu wrote:
jason@icetor.is:
yep you're correct, I should have taken note of the version numbers better. All exits have been updated now.
is atlas wrong/not up to date yet about loki2 having an uptime of 60 days and still running tor v0.2.4.22?
https://atlas.torproject.org/#details/5CECA69D0D91B5B38376B98B761BE18938297E...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
For at least 24 hours I have been noticing that statistics of my nodes like uptime and MyFamily are not updating as they used to. I issued them all a reboot and changed the config but no changes yet to be seen.
On 19-8-2014 01:33, jason@icetor.is wrote:
I'm not sure why atlas hasn't updated yet but currently loki1 is running 2.4.23. As well as loki2 and loki3. -Jason
On 08/18/2014 07:02 PM, Nusenu wrote:
jason@icetor.is:
yep you're correct, I should have taken note of the version numbers better. All exits have been updated now.
is atlas wrong/not up to date yet about loki2 having an uptime of 60 days and still running tor v0.2.4.22?
https://atlas.torproject.org/#details/5CECA69D0D91B5B38376B98B761BE18938297E...
_______________________________________________
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
- -- Tim Semeijn pgp 0x08CE9B4D
On 18/08/2014 4:48 PM, Tim Semeijn wrote:
For at least 24 hours I have been noticing that statistics of my nodes like uptime and MyFamily are not updating as they used to. I issued them all a reboot and changed the config but no changes yet to be seen.
Agreed. I just updated two of my relays today (including a reboot to one of them), but Globe hasn't registered the change yet. Uptime is continuing to accrue as if I never rebooted or restarted the relay, and the old version is still listed.
-Rex
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 8/19/2014 4:15 AM, Rex Wolf wrote:
On 18/08/2014 4:48 PM, Tim Semeijn wrote:
For at least 24 hours I have been noticing that statistics of my nodes like uptime and MyFamily are not updating as they used to. I issued them all a reboot and changed the config but no changes yet to be seen.
Agreed. I just updated two of my relays today (including a reboot to one of them), but Globe hasn't registered the change yet. Uptime is continuing to accrue as if I never rebooted or restarted the relay, and the old version is still listed.
-Rex
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
There is something going on with atlas and globe. They have huge lag. A relay is not running for 2 days (it has changed IP address and fingerprint) but still showing as running on atlas and counting uptime forward. in https://consensus-health.torproject.org everything is fine however. The same as torstatus.blutmagie.de everything fine and accurate, just atlas and globe have lag. Someone needs to look into them.
- -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11
On 19/08/14 03:25, s7r wrote:
There is something going on with atlas and globe. They have huge lag. A relay is not running for 2 days (it has changed IP address and fingerprint) but still showing as running on atlas and counting uptime forward. in https://consensus-health.torproject.org everything is fine however. The same as torstatus.blutmagie.de everything fine and accurate, just atlas and globe have lag. Someone needs to look into them.
I'll look into this today.
In the future, please feel free to open a Trac ticket in the Onionoo component (Atlas or Globe works, too) and say that there's an issue.
All the best, Karsten
On 19/08/14 09:09, Karsten Loesing wrote:
On 19/08/14 03:25, s7r wrote:
There is something going on with atlas and globe. They have huge lag. A relay is not running for 2 days (it has changed IP address and fingerprint) but still showing as running on atlas and counting uptime forward. in https://consensus-health.torproject.org everything is fine however. The same as torstatus.blutmagie.de everything fine and accurate, just atlas and globe have lag. Someone needs to look into them.
There was a bug that I may have fixed just now.
Can someone please check if Atlas and Globe now display the correct data? If not, please provide an example.
All the best, Karsten
On 19/08/2014 8:58 AM, Karsten Loesing wrote:
On 19/08/14 09:09, Karsten Loesing wrote:
On 19/08/14 03:25, s7r wrote:
There is something going on with atlas and globe. They have huge lag. A relay is not running for 2 days (it has changed IP address and fingerprint) but still showing as running on atlas and counting uptime forward. in https://consensus-health.torproject.org everything is fine however. The same as torstatus.blutmagie.de everything fine and accurate, just atlas and globe have lag. Someone needs to look into them.
There was a bug that I may have fixed just now.
Can someone please check if Atlas and Globe now display the correct data? If not, please provide an example.
All the best, Karsten
This morning, all my relays show with correct uptime and version on Globe. Thanks!
-Rex
On 08/19/2014 04:07 PM, Rex Wolf wrote:
On 19/08/2014 8:58 AM, Karsten Loesing wrote:
On 19/08/14 09:09, Karsten Loesing wrote:
On 19/08/14 03:25, s7r wrote:
There is something going on with atlas and globe. They have huge lag. A relay is not running for 2 days (it has changed IP address and fingerprint) but still showing as running on atlas and counting uptime forward. in https://consensus-health.torproject.org everything is fine however. The same as torstatus.blutmagie.de everything fine and accurate, just atlas and globe have lag. Someone needs to look into them.
There was a bug that I may have fixed just now.
Can someone please check if Atlas and Globe now display the correct data? If not, please provide an example.
All the best, Karsten
This morning, all my relays show with correct uptime and version on Globe. Thanks!
-Rex
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
loki{1..3) from Icetor all reporting in fine now! -Jason
On 19/08/14 19:08, jason@icetor.is wrote:
On 08/19/2014 04:07 PM, Rex Wolf wrote:
This morning, all my relays show with correct uptime and version on Globe. Thanks!
loki{1..3) from Icetor all reporting in fine now! -Jason
Rex, Jason, thanks for letting me know.
FYI, here's what went wrong:
https://gitweb.torproject.org/onionoo.git/commitdiff/8c0b411537449b25ebb35cb...
All the best, Karsten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
jason@icetor.is:
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org repo's yet. I'll be waiting for them first. -Jason
could you describe your problem a bit? if even you have problems with updates maybe others are having the same?
and: please consider enabling automated updates via your package manager.
On 14-08-18 03:30 PM, Nusenu wrote:
jason@icetor.is:
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org repo's yet. I'll be waiting for them first. -Jason
could you describe your problem a bit? if even you have problems with updates maybe others are having the same?
and: please consider enabling automated updates via your package manager.
i get the latest 0.2.5.x version with these apt sources lines:
deb http://deb.torproject.org/torproject.org squeeze main deb http://deb.torproject.org/torproject.org tor-experimental-0.2.5.x-squeeze main
i am curious why they arent https though.
On 08/19/2014 12:37 AM, krishna e bera wrote:
On 14-08-18 03:30 PM, Nusenu wrote:
jason@icetor.is:
actually after poking at this for a bit tonight it looks like newer packages haven't been rolled out for deb.torproject.org repo's yet. I'll be waiting for them first. -Jason
could you describe your problem a bit? if even you have problems with updates maybe others are having the same?
and: please consider enabling automated updates via your package manager.
i get the latest 0.2.5.x version with these apt sources lines:
deb http://deb.torproject.org/torproject.org squeeze main deb http://deb.torproject.org/torproject.org tor-experimental-0.2.5.x-squeeze main
i am curious why they arent https though.
I guess that wouldn't provide too many benefits. It would be really clear that you will install/update Tor and the signatures should make sure you get the correct package.
tor-relays@lists.torproject.org
-
Christian Sturm -
jason＠icetor.is -
JT Allison -
Karsten Loesing -
krishna e bera -
Nusenu -
Rex Wolf -
s7r -
Tim Semeijn