[EMAIL PROTECTED] wrote:
How i take control to my server with ssh in graphic mode, what command i need to use? my computer and my server used debian
thank you for all your help
I recently updated my remote access setup.
You want vnc tunneled through ssh. (There is even a Java applet that will tunnel vnc's rfb over ssh; I wish that had existed when I first setup vnc years ago.)
Here is the general setup. Read the documentation at the links I include for specific options (e.g. resolution settings and ways to improve latency.)
I have split this into two sections: I) Server options II) Client options
I. Server Options:
1) Access a desktop that is currently in use (i.e., access display :0, including the X login screen)
Issue: The console display is left open and visible when you are remotely using the display.
2) Access a desktop that runs as its own instance (i.e., have a desktop dedicated to remote access)
Issue: You have to start and stop vncserver each time you want to run a desktop as the same user at the console.
1) Requires: packages from unstable (or testing) vnc4server < http://realvnc.com > +modification to /etc/X11/XF86Config-4 < http://realvnc.com/v4/x0.html > x11vnc (optional) < http://www.karlrunge.com/x11vnc/ >
XF86Config-4:
add to section "Module"
---
Load "vnc"
---
add to section "Screen"
---
Option "passwordFile" "/home/<your_username>/.vnc/passwd"
---
The password file will be automatically created by the Debian vnc4server once manually run. If it's not used, no password will be required for naked vnc access. (That works if you disable incoming requests for vnc ports by firewall, subsequently requiring ssh for remote vnc.)
Before connecting, run vnc4server through the command line so that your password will be setup.
If you don't want to use vnc4server, you can use the less-efficient x11vnc.
x11vnc -display :0 -many
2)
Requires: packages from stable (or testing--optional)
vncserver < realvnc.com >
tightvncserver (from testing/unstable--better than vncserver) < tightvnc.com >
Java client applet from < tightvnc.com > (optional for naked access)
+creation of:
~/.xsession < http://www-ugrad.cs.colorado.edu/X/xsession.html >
~/.vnc/xstartup (make a copy of .xsession)
Call vncserver (or tightvncserver) from the command line to start a remote desktop. If you want to be able to access naked vnc from the web, vncserver will run its own http daemon if you specify
vncserver -httpd /full/path/to/downloaded/Java/applet/directory/
google for .xsession. A usable xsession file can be as simple as one with the line
---
exec gnome-session
---
OR
---
exec startkde
---
II. Client options
1) Local clients
Each client will use a vnc binary (e.g., vncviewer from < tightvnc.com >, or krdc for KDE) and an ssh binary (e.g. PuTTY or OpenSSH).
Open ssh, and tunnel port 590x, where x is the display number used for vnc.
Open a vnc viewer, and connect to localhost.
2) Remote clients served via Java applets Each client will go to a web site and use a Java applet ssh/vnc viewer.
A) Go to < http://www.sshtools.com/ > :: Download :: SourceForge Project page
Download SSHVnc-Applet
(You might also want to look at the SSHTerm-Applet. The SSH applet is the second Windows-compatible GPL program I know of with a GUI for sftp that allows for public-key authentication [WinSCP is the first, and FileZilla might allow for it soon].)
B) Unpack the package into a web-visible directory.
C) Make the applet available.
a. Use apache or a Web host and load the applet by using < http://myaddress/sshvnc-applet/ >. (Works with server option two.)
b. Use the vncserver http daemon. vncserver -httpd /dir/to/sshvnc/Java/applet/ (I haven't gotten this to work, but it might be possible if you make a file similar to the index.vnc the vncserver expects.) Connect using http://myaddress:580x.
c. For insecure, naked vnc without needing an external web server, use server option 2 and simply append -httpd /dir/to/Java/applet/ before issuing the server command. Connect using http://myaddress:580x. This applet is tied to accessing only your server, unlike the ssh-enabled applet.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
