diff options
| author | Philipp Zabel <philipp.zabel@gmail.com> | 2022-11-19 09:52:05 +0100 |
|---|---|---|
| committer | Philipp Zabel <philipp.zabel@gmail.com> | 2022-11-23 16:58:48 +0100 |
| commit | 133417b016c5dfbfea850ad6a2f29b1ad7162401 (patch) | |
| tree | be55a31e834c9bd96054ac10d091db997946f5c8 /man | |
| parent | 0733c8f5715a06c1109d380093d4f2e040284140 (diff) | |
| download | weston-133417b016c5dfbfea850ad6a2f29b1ad7162401.tar.gz | |
backend-vnc: Add user authentication
Let VNC clients authenticate using the local username and password of
the user weston is running as. To avoid transmitting the password in
cleartext, make TLS security mandatory.
Signed-off-by: Philipp Zabel <philipp.zabel@gmail.com>
Diffstat (limited to 'man')
| -rw-r--r-- | man/weston-vnc.man | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/weston-vnc.man b/man/weston-vnc.man index 582fe28f..5232aacb 100644 --- a/man/weston-vnc.man +++ b/man/weston-vnc.man @@ -19,8 +19,8 @@ the graphical content, depending on what is supported by the VNC client. The VNC backend is not multi-seat aware, so if a second client connects to the backend, the first client will be disconnected. -Note that authentication is not supported yet. Anyone with access to the port -can get control of the desktop via the VNC output. +The VNC client has to authenticate as the user running weston. This requires a PAM configuration file +.BR /etc/pam.d/weston-remote-access . .\" *************************************************************** .SH CONFIGURATION |