|WESTON-RDP(7)||Miscellaneous Information Manual||WESTON-RDP(7)|
The RDP backend uses FreeRDP to implement the RDP part, it acts as a RDP server listening for incoming connections. It supports different codecs for encoding the graphical content. Depending on what is supported by the RDP client, the backend will encode images using remoteFx codec, NS codec or will fallback to raw bitmapUpdate.
On the security part, the backend supports RDP security or TLS, keys and certificates must be provided to the backend depending on which kind of security is requested. The RDP backend will announce security options based on which files have been given.
The RDP backend is multi-seat aware, so if two clients connect on the backend, they will get their own seat.
- The IP address on which the RDP backend will listen for RDP connections. By default it listens on 0.0.0.0.
- The TCP port to listen on for connections, it defaults to 3389.
- By default when a client connects on the RDP backend, it will instruct weston to resize to the dimensions of the client's announced resolution. When this option is set, weston will force the client to resize to its own resolution.
- The file containing the RSA key for doing RDP security. As RDP security is known to be insecure, this option should be avoided in production.
- The file containing the key for doing TLS security. To have TLS security you also need to ship a file containing a certificate.
- The file containing the certificate for doing TLS security. To have TLS security you also need to ship a key file.
$ winpr-makecert -rdp -silent -n rdp-security
This will create a rdp-security.key file.
You can generate a key and certificate file to use with TLS security using a 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 RDP backend.