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:

In windows TurboVNC v3.0.2 there are setting for secur connections using certificates.

I have tried every combination of settings with PEM and PPK files (with Pub/Private and public only keys).
<Screenshot 2023-04-26 111747.png>


Can some point me to documentation on these options?  Internet searches turn up nada.

Thanks,
bondo

--
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/237b64d9-466b-4d55-8a89-3ee5d5dba5fan%40googlegroups.com.
<Screenshot 2023-04-26 111747.png>

--
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.

Reply via email to