reaching out to relay ops that run outdated versions
-----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
-----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT8IfkAAoJEDcK3SCCSvoecIMP/0NX+C4+h55BXaQt2RSwA472 PyEIjSRUwrlnc0navJ1pSHOusCWnrCiMFXQaQqcdCliODzEytPoaLynItiwAtKzp UhDja4Sp/Lag9m9CiNJ/0C9k9OeHQbKcEffLAnTVUOZmcBFwo2CsROruGgveOic6 gE13Yi9LuoHdtMfDDRgLoQyL5hqa1kogpj9maMjXZwEwXhZvNpd7GEUd79WjtVm+ eFoYTW4mgPXcU0fZOtuZxAAkrd/blEzr67o4aKiMeaNDo6zmXIBe1URsPkRf50dO kQ0m4/GSicdVyOnsId+f6RcpAD/LD7QiqIyxv/XZ9uEDqtI2RvxBxNeU9kXU8KK+ y4fsXKZ4pvXgj5Nqv7niNJlftegr1rrdRB7wAtZ/2ETpEL3dqC+aBo0bL+ctk1zZ RlXZkPTOTmGEh5pDxXr8P1rxukgivOsPw3tWmeCjb2+HeiRi117LNeccvwW3SZYE pDLVSJIhxpkFKxtJ8N4vTyqoQzX/N+g1gkOZ/yuF4aCIpfLFTxjUUkMt8wyEI+v2 HMiAXyeHBFh541b9ScTrLao21sxPDsQHq1mNf3RHRKESgiejWLZz74wojUU/drIP coZVoJ7U3aFqb6xgIlJzv8u+IcPld6Xsy3U8MUtD+4q2v7t9y6u6QBrj454YCQrQ Ms0g2ocOvRCTKWUgtbdx =BK/o -----END PGP SIGNATURE-----
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... -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT8k26AAoJEDcK3SCCSvoesxIP/j4gx2iAYVlaFg/CXaw8mHWg iLDTsWK4Rp3OAREVmDpIqCiOQgUbt+zehg+6TzZKhd6d4u2BFjmX0FX+mioC9rLL I5pRJR75Oqzp0N8mmAYaidBetbvPt7Y2jfnWo/PF3GXQtfMDez1zGOhUeYSqwHZD GE/0t8bdvT5/7TqYQA9e42y5FXhgjLQESVpTSo2rHSS71sBw4OdROfdbp+h2kpJk bUXBzaillW1cRxAsbM3IgzYRzk0m2HFpEnFkAV+1bCh3mGjBbL05riRuAbHraX5B Ya1IWDY4XeHhQANw2a9i1seSklbZJB6HxwPJdDdAHK5ouHYQpP/nfBXaNy5d2nhu 8nB09WMbpFpx6G8PMA81rtYSvuNn+ZnxN9ruZVfZrQX3wcPs+V0pf91t/WL9y/KA Q6OGJWQGHDJRP8N3qBg4o6mzkLx4/O4512piISoz08NGk8UQDToK5H5mgWRcX6nf HuP81WAMrAjLC2KA+GVZf93jSVHFHx+w9lWr/8eSBjJmUMiYUyxmB2CpFbixHADe uF0kw0zIanT/EacDT62m37iF23IHTjPMyX/0USPZgmar6j/8Nh/XJ67VVzlyCNJd 01uXA8wMM1cB14cp+9jcu2eTtSGAHeez1g505xJeJAmfuMMwEoIRCT/PoZ9ipApX avgP/eVc1FV3pCUKIA0Y =q9fT -----END PGP SIGNATURE-----
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT8pDNAAoJEB4F+FYIzptNWkcH/09/irUNpUpoEFd7TC/w8/TQ JzydV6NBK/9efZMx6Xmcng+1fyGH+3rjzXzZnQZW3EmS7Or5+W+5puYoY9xsGIvz kbA6GQvSXX1DifH2ONNWkFXtOb27dM93So005rmYHqSxB9bzqZyPI7kF0R5AJj3d b9Bbw1qpa8fqDiq60oTi0/wFZSYnla/ucjjYvCHVU/ZSQMjIgHU7fc7zncyAXYIZ o0T6JHjqGW3OFm7FmsZQsqXDGU6yBr8gpO0/1MsqUDaqdJ8KLOJLHpFnyraZawqO iJwj15gSRnF4hnWeEWVlYIGU/ghfezoM+UXYcJig7N/vN7h3TSIS+kjIytHC7Bw= =hKqn -----END PGP SIGNATURE-----
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT8qeHAAoJEIN/pSyBJlsRBH0IAL2kdARDPoJ4lyZ8EJlLo7pK bYXVqtlDp464tr0qQGG+vqkGmkctxtnD1qza49p2bo/A5eXxdaYoYFkn9EWSlBY1 BXSkqjZ73W9Hn4v9/z+mr1ZfijitLThDkgdHgilw+9iS19vYxz50VOk0ygUDhPVU PFr34/QtFRbZGS5fzsxeXr/2XJQ+vHrBP2yL0gLfLEUR8af/qUlZrS97t+VnNSTn Lfr/k6fhrACAQs8IY4lfRq5XTeE9zDs+jndPl+IKjqXQTNoNFWy6TQSSfLXZCgeJ 3MCW/wEiOYPv2fK2cMAi58vA8jNrBoHWegn380651TL26FpnZy9Aovnh01JvjHk= =TlO4 -----END PGP SIGNATURE-----
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. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT8lRyAAoJEDcK3SCCSvoeFXkP/3jPz0tybqAYfLxvUH17KZVx p7+ItZPjM/brU2EkOgIm9LRZxArk4GP4Tg9IwDEoYpUdFv8zK4UPV5fWExsbSQff gSV4xT9vbCQ9OdR/5a0o+LHP1bUlW9F5QbTgz4ZkZZ+Sll81+kXwNPRSHxoHKr5v r9esZU74YOwXXHVPZFQkFUEkYhbcuhQ5LYiMd4EZ6y9T4YFrgOdVvDzKAuu5/Xjt 2ghIR4E4ZX59dq44yNAZMzdB+sH8a6eeMSwxl9CPg/WpSVeIBnSaCJUfI2ec1zjh 6uPW4AGrcG4L83JSFubO64y/aPbmh6BDE9H7le+/gyf5ypow0ZYyWRl16grNNF+0 hnAIgRPYEUEqyYI4XbPLDs7zLnUrvoswoXMtJzJybsEswN3qSBCeEvDq/Isdx3/H mB6ycX4lI1/i82RXew48fssWveLuyAe5Sk2hiO60YhtWApbnGpyyfNqTD8YPE1SS bBeLKrUEnVZvWidI0yBAzh17bcJaA9sShwhrInywcGl7uiIgCZjRGUyjhukBh9Du 5xYOCZ8A+ozDlLBFCyFiNeuTNcjD/EqhApJ5+1T6uNepyeSwLjcfnQDPSL+uaDN+ H2hTyj/rJ7oG4gWvydxxLZfp/P/UW4eRmzvF+iDSu24Ui3L0i5pKHX+b61sR0HB3 6VBKdf7fvfQgbLkvxwtB =a4IC -----END PGP SIGNATURE-----
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.
participants (9)
-
Christian Sturm -
jason＠icetor.is -
JT Allison -
Karsten Loesing -
krishna e bera -
Nusenu -
Rex Wolf -
s7r -
Tim Semeijn