Difference between revisions of "Talk:Secure Shell"

From ArchWiki
Jump to: navigation, search
(SendEnv)
Line 9: Line 9:
 
I think we should add something about accent/UTF-8/encoding.
 
I think we should add something about accent/UTF-8/encoding.
 
Setting SendEnv LANG LC_*  in /etc/ssh/ssh_config (client side) would be very useful.
 
Setting SendEnv LANG LC_*  in /etc/ssh/ssh_config (client side) would be very useful.
 +
 +
== Encrypted Socks Tunnel ==
 +
 +
It would be good to add how to configure chromium to use with the socks tunnel. I recommend this:
 +
 +
Add to your .bashrc the next lines:
 +
 +
    function unblock() {
 +
        port=4711
 +
        export SOCKS_SERVER=localhost:$port
 +
        export SOCKS_VERSION=5
 +
    }
 +
 +
So, the next time you want to use chromium with the secure tunnel,
 +
 +
    unblock
 +
 +
 +
And then start chromium. You'll be using those proxy settings

Revision as of 22:02, 13 March 2011

regarding X11 forwarding: i don't think it is necessary to enable X11Forwarding on the client on a global base: "Enable the ForwardX11 option in ssh_config on the client."

simply specifing -X option to ssh works for me. [The preceding unsigned comment was added 2010-01-11T15:41:54 by Uwinkelvos (Talk | contribs).]

SendEnv

I think we should add something about accent/UTF-8/encoding. Setting SendEnv LANG LC_* in /etc/ssh/ssh_config (client side) would be very useful.

Encrypted Socks Tunnel

It would be good to add how to configure chromium to use with the socks tunnel. I recommend this:

Add to your .bashrc the next lines:

   function unblock() {
       port=4711
       export SOCKS_SERVER=localhost:$port
       export SOCKS_VERSION=5
   }

So, the next time you want to use chromium with the secure tunnel,

   unblock


And then start chromium. You'll be using those proxy settings