Connecting to Lantern before Tor (User -> Lantern -> Tor -> Internet) - old

[2xiangzi]

Thank you entr0py for sharing your opinion and knowledge！

@entr0py

I do worry that Whonix devs might get some additional unwanted attention from MSS

In my opinion, based on my observation, although whonix is a great project, it is less likely to be “cared” by CCP in near future. That’s because, due to the limitation on money/manpower, they can only focus on those “high-value” “easy-to-catch” target(ex. the author of Shadowsocks who developed a very popular censorship circumvent tool without doing any anonymous protection ). So don’t worry too much:)

By the way, even if whonix project was under pressure, we shouldn’t do self-censorship , should we?

@entr0py

Here’s what arma (Roger Dingledine) wrote

Thank you for the useful information!

@entr0py

Lantern: I’m more interested in user -> tor -> lantern -> internet

Using lantern behind Tor to avoid recaptcha may no longer be a good idea since recaptcha has appeared on at least google site when using lantern.

I’m curious about how you implement using Lantern behind Tor? A way to do this is using Privoxy:
forward-socks5t / 127.0.0.1:Tor 127.0.0.1:Lantern(8787 by default)

@entr0py

but I’ll take a look at your setup as well.

That’s great! Actually I did met some difficulties when trying to set it up, which will be described later on this post: Connecting to Lantern before Tor (User -> Lantern -> Tor -> Internet) - new

@entr0py

Example: if you have:sys-net - proxyVM - whonix-gw - ubuntu

sys-net has no firewall settings, because it’s not connected to a netVM.
Changing proxyVM’s firewall settings, changes iptables rules on sys-net
Changing ubuntu’s firewall settings does nothing because whonix doesn’t care.

That explanation is really clear and neat, thank you!