Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-19 Thread Karsten Loesing
On 19/08/14 19:08, ja...@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 wen

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-19 Thread jason
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 >

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-19 Thread Rex Wolf
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 showin

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-19 Thread Karsten Loesing
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

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-19 Thread Karsten Loesing
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 eve

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-18 Thread s7r
-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

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-18 Thread Rex Wolf
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

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-18 Thread Tim Semeijn
-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 wrot

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-18 Thread jason
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 at

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

2014-08-18 Thread Nusenu
-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://atl