Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month at the Massachusetts Institute of Technology, in Building E51.

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] vnc

> From: at [mailto:discuss-
> at] On Behalf Of Stephen Adler
> My problem with this is that the password I issue to open up the
> vncviewer window to access the desktop of the user is not part of the
> /etc/passwd file, but some clear text password file. There are warnings
> in the documentation about this.

I've seen some good replies including ssh tunnel and openvpn, but I'm surprised nobody mentioned this - 

If you run vncserver on a per-user basis, you set the password with the command "vncpasswd" which creates ~/.vnc/passwd, encrypted hashed like the /etc/passwd file.  So that problem is solved, *but* the vnc traffic itself is unencrypted.  So as others have said, you need to secure the communication channel.  I know there exists such a thing as VNC encryption, but I haven't looked into that - The solution I would personally use is ssh tunnel, because for me it's far easier than openvpn (due to familiarity).

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /