Pierre Ossman | f256a1a | 2014-09-17 14:09:58 +0200 | [diff] [blame] | 1 | .TH vncpasswd 1 "" "TigerVNC" "Virtual Network Computing" |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 2 | .SH NAME |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 3 | vncpasswd \- change the VNC password |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 4 | .SH SYNOPSIS |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 5 | \fBvncpasswd\fR [\fIpasswd-file\fR] |
| 6 | .br |
| 7 | \fBvncpasswd\fR \-f |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 8 | .SH DESCRIPTION |
| 9 | .B vncpasswd |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 10 | allows you to set the password used to access VNC desktops. Its default |
| 11 | behavior is to prompt for a VNC password and then store an obfuscated version |
| 12 | of this password to \fIpasswd-file\fR (or to $HOME/.vnc/passwd if no password |
| 13 | file is specified.) The \fBvncserver\fP script runs \fBvncpasswd\fP the first |
| 14 | time you start a VNC desktop, and it invokes \fBXvnc\fP with the appropriate |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 15 | \fB\-rfbauth\fP option. \fBvncviewer\fP can also be given a password file to |
| 16 | use via the \fB\-passwd\fP option. |
| 17 | |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 18 | The password must be at least six characters long (unless the \fB\-f\fR |
| 19 | command-line option is used-- see below), and only the first eight |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 20 | characters are significant. Note that the stored password is \fBnot\fP |
| 21 | encrypted securely - anyone who has access to this file can trivially find out |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 22 | the plain-text password, so \fBvncpasswd\fP always sets appropriate permissions |
| 23 | (read and write only by the owner.) However, when accessing a VNC desktop, a |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 24 | challenge-response mechanism is used over the wire making it hard for anyone to |
| 25 | crack the password simply by snooping on the network. |
| 26 | |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 27 | .SH OPTIONS |
| 28 | |
| 29 | .TP |
| 30 | .B \-f |
| 31 | Filter mode. Read a plain-text password from stdin and write an encrypted |
| 32 | version to stdout. Note that in filter mode, short or even empty passwords |
| 33 | will be silently accepted. |
| 34 | |
Pierre Ossman | e58fcb9 | 2018-05-07 16:03:45 +0200 | [diff] [blame] | 35 | A view-only password must be separated from the normal password by a newline |
| 36 | character. |
| 37 | |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 38 | |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 39 | .SH FILES |
| 40 | .TP |
| 41 | $HOME/.vnc/passwd |
| 42 | Default location of the VNC password file. |
| 43 | |
| 44 | .SH SEE ALSO |
| 45 | .BR vncviewer (1), |
| 46 | .BR vncserver (1), |
| 47 | .BR Xvnc (1) |
| 48 | .BR vncconfig (1), |
| 49 | .br |
Pierre Ossman | 32b96ff | 2018-10-19 14:56:53 +0200 | [diff] [blame] | 50 | https://www.tigervnc.org |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 51 | |
DRC | 7f9ea27 | 2010-07-09 19:37:14 +0000 | [diff] [blame] | 52 | .SH AUTHORS |
Pierre Ossman | e37a144 | 2014-09-17 14:08:16 +0200 | [diff] [blame] | 53 | Tristan Richardson, RealVNC Ltd., Antoine Martin, D. R. Commander and others. |
Constantin Kaplinsky | b30ae7f | 2006-05-25 05:04:46 +0000 | [diff] [blame] | 54 | |
| 55 | VNC was originally developed by the RealVNC team while at Olivetti |
Constantin Kaplinsky | be1bda8 | 2006-06-02 04:43:52 +0000 | [diff] [blame] | 56 | Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were |
Pierre Ossman | e37a144 | 2014-09-17 14:08:16 +0200 | [diff] [blame] | 57 | implemented by Constantin Kaplinsky. Many other people have since |
| 58 | participated in development, testing and support. This manual is part |
| 59 | of the TigerVNC software suite. |