Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upX509 client authentication #787
Comments
This comment has been minimized.
This comment has been minimized.
|
X509 is currently only used to authenticate the server, not the client. So basically how most web servers work. It should theoretically be possible to use client certificates as well, but this is not implemented at the moment. It could also require a protocol extension to work really well. |
CendioOssman
added
the
enhancement
label
Jan 16, 2019
CendioOssman
changed the title
X509CA option on server side
X509 client authentication
Jan 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mestag-a commentedJan 14, 2019
•
edited by CendioOssman
Is there a technical reason why the X509CA configuration option is available on the client side, but not the server side ?
I wanted to use this so that a VNC server would only accept client connections from users with a certificate signed from the configured CA.
It is possible to configure OpenVPN and SSH to trust a given CA, so I was wondering why this "trusting feature" was implemented the other way around in TigerVNC.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.