Difference between revisions of "Talk:Secure Shell"

From ArchWiki
Jump to: navigation, search
(Encrypted Socks Tunnel)
m
(7 intermediate revisions by 6 users not shown)
Line 20: Line 20:
 
         export SOCKS_SERVER=localhost:$port
 
         export SOCKS_SERVER=localhost:$port
 
         export SOCKS_VERSION=5
 
         export SOCKS_VERSION=5
 +
        chromium &
 
     }
 
     }
  
Line 26: Line 27:
 
   $ unblock
 
   $ unblock
  
And then start chromium. You'll be using those proxy settings
+
== Automatically logout all SSH users when the sshd daemon is shutdown. ==
 +
 
 +
edit /lib/systemd/system/systemd-user-sessions.service and append network.target to the after line.
 +
 
 +
 
 +
[Unit]
 +
Description = Permit User Sessions
 +
 
 +
Documentation = man:systemd-user-sessions.service(8)
 +
 
 +
After = network.target remote-fs.target
 +
 
 +
 
 +
then symlink /lib/systemd/system/systemd-user-sessions.service to /etc/systemd/system/
 +
 
 +
 
 +
[[User:Artomason|artomason]] ([[User talk:Artomason|talk]]) 20:32, 7 February 2013 (UTC)
 +
 
 +
== systemd failed to start sshd ==
 +
 
 +
It might be good to add, if {{ic|systemctl status sshd}} shows that sshd failed, try and run /usr/sbin/sshd. This way if there is a bad configuration option (ie typo in /etc/ssh/sshd_conf), it is listed with line number.
 +
 
 +
[[User:Matyilona200|Matyilona200]] ([[User talk:Matyilona200|talk]]) 13:45, 16 May 2013 (UTC)

Revision as of 13:45, 16 May 2013

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
       chromium &
   }

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

  $ unblock

Automatically logout all SSH users when the sshd daemon is shutdown.

edit /lib/systemd/system/systemd-user-sessions.service and append network.target to the after line.


[Unit] Description = Permit User Sessions

Documentation = man:systemd-user-sessions.service(8)

After = network.target remote-fs.target


then symlink /lib/systemd/system/systemd-user-sessions.service to /etc/systemd/system/


artomason (talk) 20:32, 7 February 2013 (UTC)

systemd failed to start sshd

It might be good to add, if systemctl status sshd shows that sshd failed, try and run /usr/sbin/sshd. This way if there is a bad configuration option (ie typo in /etc/ssh/sshd_conf), it is listed with line number.

Matyilona200 (talk) 13:45, 16 May 2013 (UTC)