Re: [tor-relays] Relay vs exit node

> On 19 Aug 2016, at 06:50, majacobs wrote: > > Is my understanding correct that is NOT possible to run an accesspoint that > connects to tor running a relay instead of an exit-node? > I am able to torify programs running on the system , but need the acces point > to be

Re: [tor-relays] Guard Flag without stable Flag

Well, the flag seems to be staying now, I guess it doesn't hurt anything though. On Wed, Aug 17, 2016 at 9:46 PM, Ivan Markin wrote: > George Kadianakis: > > I think this is OK. > > > > The patch that required Stable flag for Guard flag only got merged > recently: > > Just for

Re: [tor-relays] Problems with isp's onestrike policy

> On 18 Aug 2016, at 18:24, majacobs wrote: > > Block ports that spread worm(like) virii would also mean closing ports 80 and > 443. I am afraid that is no option Sadly, there's not much we can do then. Tor relays don't inspect traffic in general - there are legal and

[tor-relays] Relay vs exit node

Is my understanding correct that is NOT possible to run an accesspoint that connects to tor running a relay instead of an exit-node? I am able to torify programs running on the system , but need the acces point to be torified for some clients that need to go through tor. I am aware that this

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

Yawning Angel wrote: > Michael McConville wrote: > > I forgot to mention all the crypto required, too. These boards don't > > have crypto accelerators, so that's a big cost. > > What? I forgot to mention all the crypto required, too. These boards don't have crypto

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

On Thu, 18 Aug 2016 11:50:33 -0600 Michael McConville wrote: > I forgot to mention all the crypto required, too. These boards don't > have crypto accelerators, so that's a big cost. What? ARMv8-A has hardware accelerated SHA(1/2), AES, and a carry-less multiply. As far as I

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

Michael McConville wrote: > Roman Mamedov wrote: > > On Thu, 18 Aug 2016 10:40:00 -0600 > > Michael McConville wrote: > > > > > Zack Weinberg wrote: > > > > Has anyone had any experience running *exit* nodes on Raspberry > > > > Pi-grade hardware, or slightly beefier? We are

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

Roman Mamedov wrote: > On Thu, 18 Aug 2016 10:40:00 -0600 > Michael McConville wrote: > > > Zack Weinberg wrote: > > > Has anyone had any experience running *exit* nodes on Raspberry > > > Pi-grade hardware, or slightly beefier? We are thinking of > > > replacing the old,

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

I think you mean "if" it goes live. That ticket has been open for 4 years, and originally had a milestone for 0.2.4. On Aug 18, 2016 12:36 PM, "Pi3" wrote: > Im running 5 Mbits mid node on Pi3. Cpu load is 25-30% on 1 core with full > steady traffic - no aes-ni here. >

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

Im running 5 Mbits mid node on Pi3. Cpu load is 25-30% on 1 core with full steady traffic - no aes-ni here. Things should improve greatly when this ticket will go live in 0.2.9.x https://trac.torproject.org/projects/tor/ticket/7572___ tor-relays

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

On Thu, 18 Aug 2016 10:40:00 -0600 Michael McConville wrote: > Zack Weinberg wrote: > > Has anyone had any experience running *exit* nodes on Raspberry > > Pi-grade hardware, or slightly beefier? We are thinking of replacing > > the old, bulky, power-hungry machine currently

[tor-relays] Tiny computers (RPi-like) for exit nodes?

Has anyone had any experience running *exit* nodes on Raspberry Pi-grade hardware, or slightly beefier? We are thinking of replacing the old, bulky, power-hungry machine currently running exit 78C7C299DB4C4BD119A22B87B57D5AF5F3741A79 with something on that level. It only has to hit 10Mbps.

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?

Zack Weinberg wrote: > Has anyone had any experience running *exit* nodes on Raspberry > Pi-grade hardware, or slightly beefier? We are thinking of replacing > the old, bulky, power-hungry machine currently running exit > 78C7C299DB4C4BD119A22B87B57D5AF5F3741A79 with something on that level. > It

[tor-relays] Abuse reports for non-exits

Hi, a directory authority IP-address on the DFRI network was recently reported for hosting malware and abuse reports was sent out to several mail addresses. Not only to ab...@dfri.tld as one would hope. The reason seems to have been malware using Tor connecting to the IP while analyzed in a

Re: [tor-relays] ExoneraTor down

On 18.08.2016 09:05, Karsten Loesing wrote: > It's back now! The encoding of https://exonerator.torproject.org/ is not correct, however, at least not for the German localized variant. I have tried different web browsers to make sure it is not a problem on my end, and all umlauts are garbled (and

Re: [tor-relays] Problems with isp's onestrike policy

Hi, If you are hosting it with XS4ALL, contact them. They have a policy on Tor exits, and should be able to do something. Cheers, Thom On 18/08/16 10:24, majacobs wrote: > Block ports that spread worm(like) virii would also mean closing ports > 80 and 443. I am afraid that is no option > >

Re: [tor-relays] Problems with isp's onestrike policy

Block ports that spread worm(like) virii would also mean closing ports 80 and 443. I am afraid that is no option the white rider (Het leuke van ... is the white rider (Het leuke van ... is > On 18 aug. 2016, at 01:30, teor wrote: > > >> On 18 Aug 2016, at 08:23,

Re: [tor-relays] ExoneraTor down

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/08/16 17:19, Peter Palfrader wrote: > On Wed, 17 Aug 2016, Alexander Dietrich wrote: > >> I just tried to use ExoneraTor, but it seems to be down: >> https://exonerator.torproject.org/ > > There is some database maintenance going on. It

Re: [tor-relays] Local DNS on Exit logs failed user queries

> On 18 Aug 2016, at 15:46, Andrew Deason wrote: > > On Wed, 17 Aug 2016 12:23:15 +1000 > teor wrote: > >> Has anyone checked if the logs on other resolvers (like unbound) have >> the same issue? > > On my exit running