Found out how to do it. Since this subject is talked about in the
Documentation I figured out the problem probably laid with the
firewall... It did.

So long story short:

1) Download firefox-esr with the package manager and install whatever
plugins you need (noscript, httpseverywhere, ...)
2) Setup ssh as a tor hidden service on the remote end (this ensures the
fail close part: you won't be able to connect if you don't go through tor)

3)Punch a hole in the firewall, here I open port 9999
sed -i 's/(9050 9061 9062 9150)/(9050 9061 9062 9150 9999)/g'
/etc/ferm/ferm.conf

/usr/sbin/ferm /etc/ferm/ferm.conf

4) Open the tunnel
ssh -D 9999 -CNf [email protected]

5) Configure firefox to use it, thanks to the firewall if it's not using
your tunnel or TOR it won't connect to anything

This setup seems sound but I'd love some informed feedback about it.
Cheers!


forgottenbeast:
> Greetings,
> I'm currently working on the following setup:
> 
> 1) run a ssh server as a tor hidden service on a remote machine
> 2) Use a tails instance to connect to it over tor
> 3) Launch a browser in tails and use the ssh connection as a proxy
> 
> Goal: Have a connection over tor for webtraffic yet still have all
> outbound traffic exiting from the remote endpoint running the ssh hidden
> service
> 
> Reason: To be able to easily connect to services that block tor exit
> nodes and use facilities installed on the remote end
> 
> Problem: Using the simple ssh command:
> ssh -D 9999 -C -N [email protected] which works on other
> machines I get the "proxy refusing connections" error after configuring
> the browser to use as proxy localhost and port 9999.
> 
> Questions:
> Is there a better way to accomplish my goal?(X11 forwarding is
> atrociously slow)
> 
> What am I doing wrong?
> 
> Is that endeavor flawed from a security point of view?
> 
> Regards
> 
_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to