Difference between revisions of "Talk:Secure Shell"
(→Common errors: Arch recently dropped support for /etc/hosts.allow) |
|||
| Line 30: | Line 30: | ||
If you got this message: "ssh_exchange_identification: Connection closed by remote host", you probably need to do this: echo "sshd: ALL" >> /etc/hosts.allow | If you got this message: "ssh_exchange_identification: Connection closed by remote host", you probably need to do this: echo "sshd: ALL" >> /etc/hosts.allow | ||
| + | :[http://www.archlinux.org/news/dropping-tcp_wrappers-support/ Arch recently dropped support for /etc/hosts.allow]. -- [[User:Karol|Karol]] 10:50, 1 August 2011 (EDT) | ||
Revision as of 14:50, 1 August 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
chromium &
}
So, the next time you want to use chromium with the secure tunnel,
$ unblock
Common errors
If you got this message: "ssh_exchange_identification: Connection closed by remote host", you probably need to do this: echo "sshd: ALL" >> /etc/hosts.allow
- Arch recently dropped support for /etc/hosts.allow. -- Karol 10:50, 1 August 2011 (EDT)