Re: [tor-relays] reaching out to relay ops that run outdated versions
On 08/19/2014 12:37 AM, krishna e bera wrote: > On 14-08-18 03:30 PM, Nusenu wrote: >> ja...@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 mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Web status page
Lol, must have hit Send instead of discard. Sorry about that >.< On Monday, August 18, 2014, staticsafe wrote: > On 8/18/2014 21:51, IceFish ThreeTwo wrote: > > Is there a > > > > https://atlas.torproject.org/ > http://torstatus.blutmagie.de/ > > -- > staticsafe > https://staticsafe.ca > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -- Sent from my iPhone ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Web status page
On 8/18/2014 21:51, IceFish ThreeTwo wrote: > Is there a > https://atlas.torproject.org/ http://torstatus.blutmagie.de/ -- staticsafe https://staticsafe.ca ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Web status page
Is there a -- Sent from my iPhone ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)
-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- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)
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 signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)
-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, ja...@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: >> ja...@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/5CECA69D0D91B5B38376B98B761BE18938297E8D >> >> >> >> >> >> ___ >> 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- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)
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: > ja...@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/5CECA69D0D91B5B38376B98B761BE18938297E8D > > > > > ___ > 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
Re: [tor-relays] reaching out to relay ops that run outdated versions
On 14-08-18 03:30 PM, Nusenu wrote: > ja...@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. signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] reaching out to relay ops that run outdated versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ja...@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- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ja...@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/5CECA69D0D91B5B38376B98B761BE18938297E8D -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- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Include Tor Weather Link
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Spencer Rhodes: > If another email goes out to operators of outdated Tor relays, I > would suggest including some information and a link to the Tor > Weather service, which has an option to notify via email if the > software version is outdated. Yes I think the service perfectly fits that use case, but since it is being rewritten [1] I was not sure about its current state: https://lists.torproject.org/pipermail/tor-talk/2014-August/034268.html [1] https://lists.torproject.org/pipermail/tor-dev/2014-August/007293.html -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJT8kqpAAoJEDcK3SCCSvoe0J0QAIPbVCtahqeuUDoCstcafwJU FMyMq2LoXIsQiKxzpqH69oeTLuNY2DGkofz19Dv7idsmmmsWchDvL3rF69IHVxO6 uR/1KSMR0FaQueFyfaG5Rfj3o2XSTVWFRiSo9eE7QLqOjw7SrcVNrvmfze2atLr5 5mhobCNBw2cVWWYYrYhseTU/H7ZOKr1I4JxAYY7PyPTLo4qT/itXQkQ0uHJZVyNV Xp9NNpGSNzvLHL+ckU8mARVYqncHOmEaJ4UV4sv/Fvd50LrO75RzyPfFKQf9qKFr /xdexYdpV2q4j4/Kvy1kXs0R3HiQk5Ms1AFVplpj2CbSWA6Nf39iP7GOPGQup2ko ijktmq4XeiKv548IJe16TeZ98/Ynm7+7VjYFSEg6+A9Cgrr5ayNeM29TI5gfTrso Pt4u6so8/0IzvawuOK4RoT5zBafdWI/3OjfQ02919DjOov2mgTmwLPyPAWcDyNpx H9pIwwGQQefVl+cOyg2Q7KFsyYKH/G/IghhxAS3FAYLKuyreiTnZiCi+p4Ac674y yxd9+z8fbjXrIRio/YJPZkOVO5IFV73GmwEzX3ysYlClj39Q3ZH1hsl6ih76tTL0 QT2BouYBOD6cEyS4O11FgNSRJpoyOPHVfFJSlpAnlv7kdkqnF0g4ZqRoj7yLUPAH E1M7xAmlcNM21utvLNLM =5vYt -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Include Tor Weather Link
If another email goes out to operators of outdated Tor relays, I would suggest including some information and a link to the Tor Weather service, which has an option to notify via email if the software version is outdated. -- Sent from my phone.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Dynamic IP
Tim Wilson-Brown
E: twils...@mac.com
> Date: Mon, 18 Aug 2014 05:04:31 +0200
> From: Sebastian Hahn
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays] Dynamic IP
> Message-ID:
> Content-Type: text/plain; charset=us-ascii
>
> Hi Tim,
>
>> Sebastien, I run a relay on a machine that has an internal private IP,
>> behind a NAT router with a public IP.
>>
>> In my experience, I need to specify the NAT router's public IP in the torrc,
>> otherwise tor doesn't include it in the router descriptor it submits to the
>> consensus.
>
> This shouldn't happen typically, Tor tries to learn its IP address by
> looking at the traffic it receives.
>
>> If that process isn't working for me, is this a bug I should report?
>
> Likely. Can you try again, noting the kind of log messages Tor might
> emit?
>
I apologise, Sebastien, it appears I was not waiting long enough for the router
to connect to a directory, then use the headers to find its IP. I had always
assumed that the first series of failures to find an IP (before any directories
were contacted) was permanent.
This is the debug log output from a secondary test router that I configured on
the same IP:
Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const
or_options_t *, uint32_t *, const char **, char **)(): Guessed local hostname
'REDACTED.local' resolves to a private IP address (192.168.REDACTED.REDACTED).
Trying something else.
Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const
or_options_t *, uint32_t *, const char **, char **)(): Interface IP address
'192.168.REDACTED.REDACTED' is a private address too. Ignoring.
Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const
or_options_t *, uint32_t *, const char **, char **)(): Address 'REDACTED.local'
resolves to private IP address '192.168.REDACTED.REDACTED'. Tor servers that
use the default DirAuthorities must have public IP addresses.
Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const
or_options_t *, uint32_t *)(): Could not determine our address locally.
Checking if directory headers provide any hints.
Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const
or_options_t *, uint32_t *)(): Success: chose address
'121.REDACTED.REDACTED.REDACTED'.
Once the test router appears in the consensus, I'll make similar changes to the
primary router (and it will pick them up on the next restart!)
Tim
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
