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] icetor's loki2 update status (CVE-2014-5117)
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 ___ 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 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 ___ 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 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 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)
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 went wrong:
https://gitweb.torproject.org/onionoo.git/commitdiff/8c0b411537449b25ebb35cbac8e3cc4e3813f182
All the best,
Karsten
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Protecting your domain's reputation
Hey. Am 19.08.2014 17:51, schrieb JusticeRage: The good news is, there is something you can do about it. This is exactly what Sender Policy Framework [1] was created for. Long story short, this is some information you can put in your DNS to indicate which machines are allowed to send e-mails for the domains, and which are not (hint: the exit node should not be listed in there). You should consider adding a DMARC record as well (with the reject policy). This is a somewhat more recent standard that allows you to explicitly drop emails which do not have a DKIM signature for your domain and/or fail SPF checks. Most of the big email companies seem to respect DMARC now. See http://www.dmarc.org for details. felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
