| Constantin Kaplinsky | 64a943b | 2006-05-05 11:45:47 +0000 | [diff] [blame] | 1 | .TH vncpasswd 1 "05 May 2006" "TightVNC" "Virtual Network Computing" |
| Constantin Kaplinsky | 47ed8d3 | 2004-10-08 09:43:57 +0000 | [diff] [blame] | 2 | .SH NAME |
| 3 | vncpasswd \- change a VNC password |
| 4 | .SH SYNOPSIS |
| 5 | .B vncpasswd |
| 6 | .RI [ passwd-file ] |
| 7 | .SH DESCRIPTION |
| 8 | .B vncpasswd |
| 9 | allows you to set the password used to access VNC desktops. It stores an |
| 10 | obfuscated version of the password in the given file (default |
| 11 | $HOME/.vnc/passwd). The \fBvncserver\fP script runs \fBvncpasswd\fP the first |
| 12 | time you start a VNC desktop, and invokes \fBXvnc\fP with the appropriate |
| 13 | \fB\-rfbauth\fP option. \fBvncviewer\fP can also be given a password file to |
| 14 | use via the \fB\-passwd\fP option. |
| 15 | |
| 16 | The password must be at least six characters long, and only the first eight |
| 17 | characters are significant. Note that the stored password is \fBnot\fP |
| 18 | encrypted securely - anyone who has access to this file can trivially find out |
| 19 | the plaintext password, so \fBvncpasswd\fP always sets appropriate permissions |
| 20 | (read and write only by the owner). However, when accessing a VNC desktop a |
| 21 | challenge-response mechanism is used over the wire making it hard for anyone to |
| 22 | crack the password simply by snooping on the network. |
| 23 | |
| 24 | .SH FILES |
| 25 | .TP |
| 26 | $HOME/.vnc/passwd |
| 27 | Default location of the VNC password file. |
| 28 | |
| 29 | .SH SEE ALSO |
| 30 | .BR vncviewer (1), |
| 31 | .BR vncserver (1), |
| 32 | .BR Xvnc (1) |
| 33 | .BR vncconfig (1), |
| 34 | .br |
| Peter Åstrand | 9fb4e0e | 2004-12-30 10:03:00 +0000 | [diff] [blame] | 35 | http://www.tightvnc.com |
| Constantin Kaplinsky | 47ed8d3 | 2004-10-08 09:43:57 +0000 | [diff] [blame] | 36 | |
| 37 | .SH AUTHOR |
| 38 | Tristan Richardson, RealVNC Ltd. |
| 39 | |
| Peter Åstrand | 9fb4e0e | 2004-12-30 10:03:00 +0000 | [diff] [blame] | 40 | VNC was originally developed by the RealVNC team while at Olivetti |
| 41 | Research Ltd / AT&T Laboratories Cambridge. TightVNC additions was |
| 42 | implemented by Constantin Kaplinsky. Many other people participated in |
| 43 | development, testing and support. |