On Tue, April 3, 2018 11:42 pm, Giulio wrote:
> Just a note, it all depends on your threat model. Be careful that most of
> the solutions you explained have each very different implications: 1) Most
> website with a login do have https. If they are hidden services they do
> not need it as traffic does not go through an exit node. If none of the
> above apply you could still use a VPN or a tunnel on top of tor but you
> will loose some anonimity
I think you're saying many otherwise HTTP only sites still use HTTPS for
the login step (but not all)!
> 3) Not using tor in order to download files prevent only man in the
> middles attack coming from the tor network, your provider, your
> neighbors, your dns server etc may still tricks you the same way.
To jsnow's question on this, file modifications can be automated. The
attacker could have a selection of files already modified, then watch for
anyone trying to download it and substitute the poisoned one. Probably
other ways to dynamically patch filetypes (like all .EXE for example) on
the fly too. Check out "Quantum Insert". Tor helps here because it's much
more difficult to target specific recipients for poisoned files, so they
have to be sent to everyone who requests them which increases the
likelihood they will get discovered. Of course, that's not the case if
you're logging in to something.
> As a general rule, mixing any of your tor activities with your non tor
> activities do break the very purpose of tor, especially if you use the
> same accounts in and out. My suggestion is to first try to understand
> what the purpose of tor is and against which type of adversary you need
> protection and then make your choices on that basis.
What Giulio said. Sounds like the OP has a good understanding of the
various weaknesses and trade-offs.