You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
The TLS_OPT_PEER_NAME option needs to be implemented, documented and tested. This option should be able to be set in conjunction with authentication methods to restrict the name of the authenticated peer (SRP: username, Cert: Subject).
The ideal situation would be to make this a simple string. However, one question is how to use TLS_OPT_PEER_NAME with getsockopt() after authentication. For SRP or PSK, this should be the authenticated username. I think for Certificates this should be the subject. This means users who want access to subjectAltName will have to parse the certificate. But I think this is the most straightforward behavior.
The text was updated successfully, but these errors were encountered:
Originally reported by @npmccallum.
The
TLS_OPT_PEER_NAME
option needs to be implemented, documented and tested. This option should be able to be set in conjunction with authentication methods to restrict the name of the authenticated peer (SRP: username, Cert: Subject).The ideal situation would be to make this a simple string. However, one question is how to use
TLS_OPT_PEER_NAME
with getsockopt() after authentication. For SRP or PSK, this should be the authenticated username. I think for Certificates this should be the subject. This means users who want access tosubjectAltName
will have to parse the certificate. But I think this is the most straightforward behavior.The text was updated successfully, but these errors were encountered: