WESTON-RDP(7) | Miscellaneous Information Manual | WESTON-RDP(7) |
weston-vnc - the VNC backend for Weston
weston --backend=vnc
The VNC backend allows to run a weston environment without the need of specific graphic hardware, or input devices. Users can interact with weston only by connecting using the remote framebuffer protocol (RFB).
The VNC backend uses Neat VNC to implement the VNC part, it acts as a VNC server listening for incoming connections. It supports different encodings for encoding 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.
The VNC client has to authenticate as the user running weston. This requires a PAM configuration file /etc/pam.d/weston-remote-access.
The VNC backend uses the following entries from weston.ini.
When the VNC backend is loaded, weston will understand the following additional command line options.
You can generate a key and certificate file to use with TLS security using typical openssl invocations:
$ openssl genrsa -out tls.key 2048 Generating RSA private key, 2048 bit long modulus [...] $ openssl req -new -key tls.key -out tls.csr [...] $ openssl x509 -req -days 365 -signkey tls.key -in tls.csr -out tls.crt [...]
You will get the tls.key and tls.crt files to use with the VNC backend.
weston(1)
2017-12-14 | Weston 14.0.1 |