The X.509 private key and certificate need to be configured on the server end. They can be specified using the -x509cert and -x509key options to vncserver or the equivalent turbovncserver.conf variables. If unspecified, vncserver will try to use ~/.vnc/x509_cert.pem and ~/.vnc/x509_key.pem, if they exist. The X.509 CA cert and CRL in the TurboVNC Viewer are only necessary if you self-signed your certificate or used a certificate authority whose root certificate is unknown to Java. Even then, I have never found that I needed to specify the CRL with self-signed certificates— just the CA cert. On Apr 26, 2023, at 11:24 AM, john bond <[email protected]> wrote:
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/B0C7857C-55D2-487D-88D8-6F4FAB5FACEF%40virtualgl.org. |
Re: [TurboVNC-Users] Security types???
'DRC' via TurboVNC User Discussion/Support Wed, 26 Apr 2023 11:25:57 -0700
- [TurboVNC-Users] Security types... john bond
- Re: [TurboVNC-Users] Secur... 'DRC' via TurboVNC User Discussion/Support
