Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
learn.adafruit.com
Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
1–10 of 21 posts
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#2See also: The Grugq's PORTAL of Pi project: https://github.com/grugq/PORTALofPi and its cousin for OpenWRT-based personal routers: https://github.com/grugq/portal
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#3If you want to run a headless Tor relay, I highly recommend using this graphical monitoring client called 'arm'
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#4[Might I hijack this thread? Yes? Thank you.]
OT: I looked at adding a TOR proxy to my personal VPS and pretty quickly decided against it* since it's tough to limit the proxy to legitimate traffic. By "legitimate traffic", I mean traffic for people who really need privacy. By "really need", I don't mean Bittorrent (yes, I use it, too, but I'll deal with the consequences), porn, etc.
I'm really not interested in running a bunch of not-mine-but-pisses-off-Comcast traffic on my cable modem, but I'd love to run a TOR proxy. Anyone got any pointers on running an effective, not-annoying proxy?
Back on topic: if I can sort the question of how to limit not-awesome traffic, I'd happily run a TOR exit node on my Linode and I'd buy a Rasperry Pi to run one at home.
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#5Some people who are running tor on their pis are getting messages about your computer being to slow. If you see these messages and are curious about the cause arma posted a good explanation today to tor-relays:
The current theory is that these happen when your relay becomes the hidden service directory, or introduction point, for a popular hidden service. So these are basically roving hotspots that move around the network. In the case of the hidden service directory the pain lasts about a day, and in the case of the introduction point, it lasts for some function of the duration of the introduction point (could be a while) and the time that the hidden service descriptor is fresh (15 minutes or so). Based on the logs here, it sounds like it might be the introduction point in these cases.
Here are some tickets to look at:
https://trac.torproject.org/projects/tor/ticket/3825
https://trac.torproject.org/projects/tor/ticket/4862
https://trac.torproject.org/projects/tor/ticket/8950
Also, the switch to the new ntor circuit-level handshake should reduce the cpu requirements for create cells (in addition to being more secure). So once more people have switched to ntor, these hotspots shouldn't be so bad. It is unclear if that's the same as 'shouldn't be bad'. :)
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposa...
Full context:
https://lists.torproject.org/pipermail/tor-relays/2013-June/...
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#6[Might I hijack this thread? Yes? Thank you.] OT: I looked at adding a TOR proxy to my personal VPS and pretty quickly decided against it * since it's tough to limit the proxy to legitimate traffic . By "legitimate traffic", I mean traffic for people who really need privacy. By "really need", I don't mean Bittorrent (yes, I use it, too, but I'll deal with the consequences), porn, etc. I'm really not interested in run…
If node operators could pick and choose whose traffic they carried tor would not be what it is.
If you dont want to handle the stress of dealing with exit traffic run a relay only node:
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#7[Might I hijack this thread? Yes? Thank you.] OT: I looked at adding a TOR proxy to my personal VPS and pretty quickly decided against it * since it's tough to limit the proxy to legitimate traffic . By "legitimate traffic", I mean traffic for people who really need privacy. By "really need", I don't mean Bittorrent (yes, I use it, too, but I'll deal with the consequences), porn, etc. I'm really not interested in run…
If node operators could pick and choose whose traffic they carried tor would not be what it is. If you dont want to handle the stress of dealing with exit traffic run a relay only node: https://www.torproject.org/docs/faq.html.en#ExitPolicies
Agreed, but one can hope, yes? For example, if I could probably kill not-interesting traffic if I could traffic-shape the traffic (e.g. you can't run more than 10kB/s averaged over 60 seconds through my node, which is plenty to browse the web securely but isn't enough to download Star Trek 2.) The question remains: are there ways to manage (not prevent) this issue?
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#8Earlier quoted context omitted.
If node operators could pick and choose whose traffic they carried tor would not be what it is. If you dont want to handle the stress of dealing with exit traffic run a relay only node: https://www.torproject.org/docs/faq.html.en#ExitPolicies
Agreed, but one can hope, yes? For example, if I could probably kill not-interesting traffic if I could traffic-shape the traffic (e.g. you can't run more than 10kB/s averaged over 60 seconds through my node, which is plenty to browse the web securely but isn't enough to download Star Trek 2.) The question remains: are there ways to manage (not prevent) this issue?
No, I don't hope. If relay operators can "peel back the layers of my onions" and see the traffic the entire security model is out the window.
Edit: I just saw your restatement of your question. Check out the bandwidth management features and set your relay to only allow exit traffic to port 443. More info on the bandwidth management can be found here:
https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#Wha...
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#9Tor being pitched as a one-stop privacy solution like this is going to backfire bad at some point in the future. It is good that they have the warning about cookies, but there are a hell of a lot of other ways you can be identified.
You simply shouldn't be using the same machine you use with your real identity with an identity that needs to be anonymous. Even simply things like ntp time sync request can give you away, let alone features like Windows Update (which will definitely give you away since they send a machine ID), browser fingerprinting, evercookies, etc.
Nobody can think of all the different things a machine can send that need to be blocked or reset, which is why you just use a fresh new machine. It is the only way to use Tor safely.
Any device that makes it easier to use Tor with your existing computer is bad for privacy. Especially something being pitched as an 'on/off' switch for instant privacy.
edit: A good setup is the following: install virtualbox, install a light-weight linux distro as a tor router, setup a private and isolated network behind it and then install your 'client' operating system on that private and isolated network in a second virtual machine. Never use the same client machine for long and use the virtual machines snapshot feature to blow away your data every x hours/days (and never use the suspend feature of virtual machine software, it saves your memory (with passwords, keys, etc.) onto disk).
Re: Onion Pi - Make a Raspberry Pi Into a Anonymizing Tor Proxy
#10Tor being pitched as a one-stop privacy solution like this is going to backfire bad at some point in the future. It is good that they have the warning about cookies, but there are a hell of a lot of other ways you can be identified. You simply shouldn't be using the same machine you use with your real identity with an identity that needs to be anonymous. Even simply things like ntp time sync request can give you away…
There is some more indepth info on problems with trusting Tor (or any off the shelf "anonymity" solution) here: http://grugq.github.io/blog/2013/06/14/you-cant-get-there-fr...
Also there's a more secure version of the RaspberryPi Tor router here: https://github.com/grugq/PORTALofPi
It was submitted by someone last night under a terrible title, so it died a sad death in the "new" page.