|
OpenBSD Security Functionally paranoid! |
|
Thread Tools | Display Modes |
|
||||
Step 1: Read the TightVNC FAQ. It states:
Quote:
Step 2: Read the vncserver(1) man page. You will discover that it is a wrapper script for the Xvnc X11 server. Step 3: Read the man page for w(1). You will learn that it merely reads the information in /var/run/utmp, and produces output from it in human readable form. Step 4: In w(1), note the SEE ALSO section recommends the utmp(5) man page. Read it, and learn that it tracks log in and log out of users. It should become clear that users connecting to the tightvnc server are not logging in, they are merely connecting to the Xvnc daemon. Step 5: Read the Xvnc(1) man page. Note, under the BUGS section, that it says (higlight mine): Quote:
|
|
||||
Unless you are using your computer only as a terminal to a powerful computer in which case you should learn about Thin clients and Trivial File Protocol I am having hard time to understand the purpose of VNC.
Most people want to run VNC in order to see their graphic applications (X client). You can see those X clients on your work station using local X server even though X client runs on the remote machine. Code:
$ ssh -Y username@server $ password ssh server$ (type now the name of your favorite X client ) |
|
||||
Here's three ....
|
|
||||
Quote:
1. Win what? Last time I checked Windows is running X server without any problems. Xming is native X server for Windows platform. Cygwin is not the most native way to run X server on Windows but it is never the less very good way of running X server and lots of other GNU software. 2. Sure. One of the most efficient network protocol is Trivial File Transfer Protocols. It is used in well known concept of Thin Clients. It is far more efficient than any VNC stuff I have seen. 3. There are Java based clients that can be used inside of your browser to get GUI access to remote desktop. It is even less efficient than VNC. I have used VNC in the past. My favorite client is SSVNC but when run properly ssvnc is more or less GUI for ssh. I would really like to hear more convincing argumentation. Last edited by Oko; 19th November 2008 at 09:37 PM. |
|
||||
On your server, start the VNC daemon, listening on localhost only.
On your workstation, use something like this: Code:
ssh -l mfaridi -L 5900:localhost:5900 your.vnc.server VNC will then connect to your VNC server like this: Code:
VNC client -> workstation:localhost:5900 -> ssh -> your.vnc.server:localhost:5900 Last edited by DutchDaemon; 20th November 2008 at 10:26 AM. |
|
||||
Quote:
Quote:
Quote:
(OH, and like you, I hate these quote wars. I think its the first time I've done it, and i have already apologized to my own sensitivities, as I do now to yours.)
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. Last edited by robbak; 21st November 2008 at 12:25 AM. Reason: dyslxeai |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
connect to OpenBSD BOX with VNC | mfaridi | OpenBSD General | 9 | 14th April 2010 08:38 PM |
please help me understand wpa settings | gosha | OpenBSD General | 1 | 14th July 2009 11:37 AM |
connect to openbsd box (ssh) | milo974 | Other BSD and UNIX/UNIX-like | 4 | 3rd January 2009 02:44 AM |
FTP-Proxy cannot connect | plexter | OpenBSD Packages and Ports | 6 | 11th October 2008 05:59 PM |
wpa_supplicant won't connect to AP | adamk | FreeBSD General | 4 | 24th September 2008 08:09 AM |