Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

On 02/09/2017 07:25 PM, teor wrote: >> I haven't been able to upgrade from Tor 0.2.7.5, which ARM tells me in >> red type is "unrecommended," which seems alarming. I'm running >> 3.2.0-121-generic-pae GNU/Linux on Ubuntu 12.04 (precise). > > If you're on Ubuntu (or Debian) you can get the

Re: [tor-relays] Reaching out to webiron

> On 10 Feb 2017, at 13:13, Andrew Deason wrote: > >>> From my current conversation with them, they are aware of at least some >>> suggested ways of blocking tor entirely, but claim some issues with >>> doing so. (Something having to do with exit node IPs changing too >>>

Re: [tor-relays] Reaching out to webiron

On Wed, 8 Feb 2017 15:42:21 +0100 Ralph Seichter wrote: > I'd like to add that the tone of the e-mails I received was quite > aggressive, threatening "blocking your whole business". Yes, I left this out of my own report, but this is similar to my own experience.

Re: [tor-relays] Reaching out to webiron

On Wed, 8 Feb 2017 17:55:34 +1100 teor wrote: > I'd be happy to talk to them, but perhaps the tor-access list is the > best forum: > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-access > > I'd be willing to discuss their goals and how they could achieve them, >

Re: [tor-relays] Reaching out to webiron

On Wed, 8 Feb 2017 18:22:33 +1100 teor wrote: > > On 8 Feb 2017, at 18:03, Andrew Deason wrote: > > > And they even gave instructions for how to block ranges from individual > > exits: > >

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

> On 10 Feb 2017, at 13:19, Kenneth Freeman wrote: > > > > On 02/09/2017 02:10 PM, Roger Dingledine wrote: >> On Thu, Feb 09, 2017 at 09:51:14PM +0100, Maarten A. wrote: >>> My log indicates Tor 0.2.5.12 (git-6350e21f2de7272f) >> [...] >>> I think I read somewhere debian

Re: [tor-relays] Normal to lose stable/guard flags on relay reboot?

> On 10 Feb 2017, at 08:56, a tor op wrote: > > Mine is still missing the guard flag after 17 days since reboot. Your bridge, or your relay? I'm happy to help with relays, and fingerprints can be made public. Bridges are a bit more complicated, and fingerprints should

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Looks like FreeBSD and most people running BSD is (are) lacking behind - "sudo pkg update && sudo pkg upgrade -y" is not bringing success - what do you recommend there? Thanks Paul Am 09.02.2017 um 22:10 schrieb Roger Dingledine: > On Thu, Feb 09, 2017 at 09:51:14PM +0100, Maarten A. wrote:

Re: [tor-relays] *** Spam *** Re: Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Thats nifty! Thank you very much. niftybunny ab...@to-surf-and-protect.net > On 9 Feb 2017, at 23:15, nusenu wrote: > >> could you please tell me which three rodents are still not updated? > > If you do not know where you run what version, you can ask onionoo to >

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Sorry, I thought I had. I must have hit the wrong reply button. Now copied in. Apologies for the top post...On 9 Feb 2017 21:58, Roger Dingledine wrote: > > On Thu, Feb 09, 2017 at 09:57:03PM +, mick wrote: > > Done > > > > Now running 0.2.9.9. > > Thanks! Can you send this to the list

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

> could you please tell me which three rodents are still not updated? If you do not know where you run what version, you can ask onionoo to give you a list of relays with a given contact string: https://onionoo.torproject.org/details?contact=ab...@to-surf-and-protect.net=platform,nickname

Re: [tor-relays] Normal to lose stable/guard flags on relay reboot?

Mine is still missing the guard flag after 17 days since reboot. Original Message Subject: Re: [tor-relays] Normal to lose stable/guard flags on relay reboot? Local Time: February 6, 2017 12:04 AM UTC Time: February 6, 2017 12:04 AM From: dl1...@gmx.de To:

Re: [tor-relays] *** Spam *** Re: Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

sigh. 3 out of 33 is not too bad, right? could you please tell me which three rodents are still not updated? niftybunny ab...@to-surf-and-protect.net > On 9 Feb 2017, at 22:45, nusenu wrote: > > > > Nick Mathewson: >> there are still 700 crashable relays on the

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Nick Mathewson: > there are still 700 crashable relays on the network. The account for ~12% CW fraction. Sadly big operators are on that list as well, i.e: +---+-+ | contact | tor_version |

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

On Thu, Feb 09, 2017 at 09:51:14PM +0100, Maarten A. wrote: > My log indicates Tor 0.2.5.12 (git-6350e21f2de7272f) [...] > I think I read somewhere debian does security backport, hence the old > version numbers. You probably know this already. > > I'm running Debian GNU/Linux 8.7 (jessie) Yep,

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Rodger, My log indicates Tor 0.2.5.12 (git-6350e21f2de7272f) apt-cache output: tor: Installed: 0.2.5.12-4 Candidate: 0.2.5.12-4 Version table: *** 0.2.5.12-4 0 500 http://ftp.nl.debian.org/debian/ jessie/main amd64 Packages 500 http://security.debian.org/

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

2017-02-09 20:48 GMT+01:00 mick : > > Attempting an upgrade from 0.2.9.8 I get nothing. > > I have Jessie and tor from jessie-backports, tor version is 0.2.9.9. Sebastian ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

On Thu, Feb 09, 2017 at 07:48:10PM +, mick wrote: > I am. (Debian Jessie 8.7 - using the tor repos). > > Attempting an upgrade from 0.2.9.8 I get nothing. Weasel suggests that you run "apt-cache policy tor" and remember what it says, then "apt-get update", then "apt-cache policy tor" again

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

On Thu, 9 Feb 2017 13:36:56 -0500 Roger Dingledine allegedly wrote: > On Thu, Feb 09, 2017 at 01:04:30PM -0500, Nick Mathewson wrote: > > If you are on some earlier version of 0.2.9.x, it would be really > > great if you could update your relay some time soon > > And, if you're

Re: [tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

On Thu, Feb 09, 2017 at 01:04:30PM -0500, Nick Mathewson wrote: > If you are on some earlier version of 0.2.9.x, it would be really > great if you could update your relay some time soon And, if you're one of the many relays still on 0.2.9.8, and the reason is something other than "oops, you're

[tor-relays] Reminder: If you are on 0.2.9.x, make sure you are running 0.2.9.9

Hi, awesome relay operators! About two weeks ago, we put out 0.2.9.9, to fix a significant problem in our build process that led to an easy remote crash attack: o Major bugfixes (security): - Downgrade the "-ftrapv" option from "always on" to "only on when

Re: [tor-relays] Hostname in DirAuthority config

Thanks for the clarification, I've managed to get it going with a few scripts to edit my torrc on start. On 8 February 2017 at 06:49, teor wrote: > > > On 8 Feb 2017, at 02:53, Andrew Smith wrote: > > > > OK, thanks for the clarification and

Re: [tor-relays] Reaching out to webiron

Two IPs in the US, one is FiOS.. I'm thinking they didn't even bother to hide, but that may be the case, sure. The FiOS IP is static. > On 9 Feb 2017, at 08:19, Mirimir wrote: > >> On 02/08/2017 11:25 AM, DaKnOb wrote: >> So less than 24 hours after the previous post and