On 7/15/15, 7v5w7go9ub0o <
7v5w7g...@gmail.com> wrote:
>
>
> On 07/14/2015 07:55 PM, Unman wrote:
>> On Thu, Jul 09, 2015 at 12:23:28PM -0700, Otto Kratik wrote:
>>> I set up and configured TorVM (on Qubes R2) some time ago according to
>>> the
>>> official instructions, and it seems to work well as intended, for every
>>> purpose imaginable and not just browsing (email, FTP, chat, video etc).
>>> But
>>> I've never seen mention before of adding a "TorFW" on top of this. Where
>>> is
>>> there a description or guide for this extra step?
>>>
>
>
> Thank you for posting this.
>
> I am NOT trying to be argumentative - I don't understand and will post
> questions as statements:
>> It was Joanna who first pointed out that the TorVM wont honour firewall
>> rules set for downstream VMs.
>
> IIUC,
> 1. She was referring to typical firewall protections (e.g. stateful
> packet control, syn cookies, etc) and was thereby suggesting that TorVM
> go out via the firewallVM!?
Did I miss a link to the archived comments? I'll need the context to
comment on this.
> 2. What other "downstream VMs" would one want?
If TorVM is effectively a router, then the downstream VMs would be
things like your e-mail client, web browser, ftp client, and so forth.
If the TorVM is a box with your apps and Tor all in one, then I
wouldn't expect there to be any downstream VMs.
>
>> If you want to use firewall rules to
>> enforce separation then you have to insert a fw between the client and
>> the TorVM:that's the TorFW.
>> One thing to be wary of, that I've pointed out before: if you simply use
>> a standard qubes fw then you get to enforce network level policies BUT
>> the
>> TorFW will alias all clients to the same IP address, so you lose the
>> benefit of stream isolation in the TorVM.
>> This is almost certainly not what you want.
>
> 3. It used to be argued that a single outbound TOR connection was better
> because it is "busier" and therefor more resistant to timing attacks!?
I haven't seen any evidence that would make you more resistant to
timing attacks. For example, there's a timing attack where the
attacker views the traffic at a Tor user's ISP, and at the datacenter
of the server they are suspected of visiting. If the attacker sees
packets arrive at the server, which came from a Tor exit node, all
they have to do is check to see if these packets emanated from the Tor
user in question just a few ms prior.
There's been a lot of good academic work on deanonymizing Tor[1]. If
you haven't already read "Users Get Routed: Traffic Correlation on Tor
by Realistic Adversaries"[2], it might be a good place to start. Of
course, you'll want to read the related work too.
[1]
http://scholar.google.com/scholar?hl=en&as_sdt=0,39&q=deanonymizing+tor
[2]
www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA602282
> 4. Is stream isolation intended to assure different exit nodes? At exit
> point, is there a way to correlate the traffic to the same client!?
I'm not familiar with "stream isolation" in this context. If you are
using a TorVM as a router, I would expect all of the downstream VMs to
share a pool of Tor routes, but I haven't verified this myself. Tor
settings may have an affect on this. See academic work above for
correlation attacks from the exit node (as well as other points in the
network).
As for the user who suggested using a VPN in place of Tor, it depends
on the threat model. If a user is concerned that their adversary can
break Tor, would it be unreasonable to think that they can break VPNs
too?
For the threat models where a VPN is an acceptable replacement, one
should be aware of a recent academic paper[3] which shows that the
majority of VPN providers leak information, such as IPv6 addresses.
If a VPN is being used in place of Tor, this is probably something
that is important. In fact, the authors even mention "Tor vs VPN" in
the conclusion section.
[3]
http://www.eecs.qmul.ac.uk/~hamed/papers/PETS2015VPN.pdf