Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
en:handbook:ssh [2015/11/12 12:41] bellard X11, VNC |
en:handbook:ssh [2015/11/12 19:45] (current) linea |
||
---|---|---|---|
Line 47: | Line 47: | ||
===== Dropbear and the X server ===== | ===== Dropbear and the X server ===== | ||
- | Dropbear supports X11 tunneling on the server side only. The client dbclient has no support for X11 tunneling. SliTaz provides a tiny shell script named ///usr/bin/sshx// to do the stuff. It open a terminal with remote X11 protocol support if the environment variable //DISPLAY// is set. You can launch any remote X windows application on this terminal. | + | Dropbear supports X11 tunneling on the server side only. The client dbclient has no support for X11 tunneling. SliTaz provides a tiny shell script named ///usr/bin/sshx// to do the work. It opens a terminal with remote X11 protocol support if the environment variable //DISPLAY// is set. You can launch any remote X windows application on this terminal. |
===== Dropbear and VNC ===== | ===== Dropbear and VNC ===== | ||
SliTaz provides a tiny VNC client named ///bin/fbvnc//. The VNC connections are not secure (neither encryption nor authentication). A tiny shell script named ///usr/bin/sshfbvnc// move the VNC connection to a SSH tunnel ending at the localhost interface of the remote VNC server. You will have an encrypted connection and authentication for your VNC sessions. | SliTaz provides a tiny VNC client named ///bin/fbvnc//. The VNC connections are not secure (neither encryption nor authentication). A tiny shell script named ///usr/bin/sshfbvnc// move the VNC connection to a SSH tunnel ending at the localhost interface of the remote VNC server. You will have an encrypted connection and authentication for your VNC sessions. |