if you try to setup tunneling in the ssh clients mostly the client will crash. the easy way is to find the config file for ssh client in the folder<\/p>\n
C:\\Users\\kamarj\\AppData\\Roaming\\SSH<\/pre>\neach profile will be stored as default.ssh2 or jc.ssh2 (the two profiles that i have now).
\nOpen the file in a text editor and type the following for tunneling vnc through ssh2<\/p>\n[Outgoing Tunnels]\r\nTunnel=S:vnc,5901,localhost,5901,1,tcp\r\nTunnel=S:vnc2,5902,localhost,5902,1,tcp<\/pre>\nsave the file and restart the client. you will see the tunneling options appear in the corresponding tab.<\/p>\n
tunnel ports<\/h3>\n
ssh -N -l someuser -L 143:localhost:143 -L 25:localhost:25 jaya.homelinux.org<\/p>\n
Forward X11<\/h3>\n
if you want to forward X through ssh we call as follows
\nssh -X jc@servername
\nif you find that you cannot open any X clients and we get the following error message
\nxterm Xt error: Can’t open display:
\nxterm: DISPLAY is not set
\nthen you can find out what is happening by using the following
\nssh -X -v jc@servername
\nwhich will give verbose information such as
\ndebug1: Requesting X11 forwarding with authentication spoofing.
\ndebug1: Remote: No xauth program; cannot forward with spoofing.
\nthen xauth was not installed.
\nthis xauth is part of the package xbase-clients.<\/p>\nSSH login Banner<\/h3>\n
I always that it is cool to get the banner that gives some security warning before you login to the server. My school systems had it and never bothered to install it in mine.
\nOpen \/etc\/ssh\/sshd_config
\nuncomment or add this line<\/p>\nBanner \/etc\/issue.net<\/pre>\nEdit the file issue.net with the contents that you want to display. now you got a dialog box with the message. The other type of message is motd or “Message of the day”. just edit the file \/etc\/motd and that will be printed everytime you login.
\n———–18-August-2006.<\/p>\nSSH Server Configuration<\/h3>\n
I had some problem with the debian SSH server for some time. It is not that i can’t use it at all. The problem is with the authentication. It is something like challenge\/response authentication which i never liked. I wanted to change it to normal Password authentication and no luck. Finally I got it from someplace\u00a0here<\/a>. All i had to was to configure the server to accept Password Authentication instead of the default Public Key Authentication.
\nOpen the \/etc\/ssh\/sshd_config file
\nLocate the line below in config file<\/p>\nPasswordAuthentication yes\r\n ChallengeResponseAuthentication no\r\n PubKeyAuthentication no<\/pre>\nand disable the above option by place a # in front of it.
\n——————06\/28\/04<\/p>\nX11 over SSH for Root<\/h3>\n
May be I’m not lucky anymore. usually whenever i have trouble, i google it and within two or three tries, i get the answer, because i had the correct keywords. This is the problem I had
\nI ssh to my debian machine from my work laptop(windows 2000, cygwin X Server), forward X11 and run X application. Suddenly one fine day I cannot run application esp “make xconfig” as a super user.
\nI got different error messages<\/p>\nX11 server shutdown \r\nX11 server reset<\/pre>\nmy google result didn’t get me any answer, because my keywords were not good enough. But i got the perfect keyword, which was<\/p>\n
X11 connection rejected because of wrong authentication<\/pre>\n