Gijs wrote:
> Why not run something like "redsocks" (first hit on transparent socks)
> http://darkk.net.ru/redsocks/ on VM1 ? It is a program that sits in between
> the proxy and client. You then configure the firewall running on VM1 to
> redirect traffic only through redsocks and allow no other
On 11.01.2012 21:40, Kyle Williams wrote:
> I would recommend you download this ASAP if you want it as I'm dumping my
> hosting provider at the end of the week and I haven't picked a replacement
> yet.
Thanks for pointing that out. Although it is deprecated, I don't think
the world needs to lose i
1) You didn't e-mail me or coderman directly and
2) I don't always stay on top of the Tor mailing list so
3) Here's your open source solution the Tor project paid us for.
http://janusvm.com/tor_vm/
For whatever reason, ask Roger or someone else, Tor VM isn't hosted on the
torproject.org site anym
Why not run something like "redsocks" (first hit on transparent socks)
http://darkk.net.ru/redsocks/ on VM1 ? It is a program that sits in between
the proxy and client. You then configure the firewall running on VM1 to
redirect traffic only through redsocks and allow no other connections.
I'd use F
Thank you for checking!
>> https://trac.torproject.org/projects/tor/wiki/doc/TorVPN
>
> The VM isn't rewriting your resolv.conf. It's either dhcpd or
> some other network configuration wizard on the host. Find it
> and use it's capabilities, or shut it down and do manual.
You were right. The mini
> https://trac.torproject.org/projects/tor/wiki/doc/TorVPN
The VM isn't rewriting your resolv.conf. It's either dhcpd or
some other network configuration wizard on the host. Find it
and use it's capabilities, or shut it down and do manual.
Try to use simpler network addressing instead of random
I
> > The goal is to create a bulletproof environment where nothing can leak
> > thought configuration mistakes, dns, java, flash, plugins and even side
> > channel attacks, local infections, trojans...
> > Additionally it's also nice to know that all applications can be torified
> > even if they
> The goal is to create a bulletproof environment where nothing can leak
> thought configuration mistakes, dns, java, flash, plugins and even side
> channel attacks, local infections, trojans...
> Additionally it's also nice to know that all applications can be torified
> even if they do not sup
The goal is to create a bulletproof environment where nothing can leak thought
configuration mistakes, dns, java, flash, plugins and even side channel
attacks, local infections, trojans... Additionally it's also nice to know that
all applications can be torified even if they do not support proxy
