-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: document s2n_cert_auth_type behavior #4454
Conversation
offline comments:
|
api/s2n.h
Outdated
* - Optional: request the client's certificate and validate if it's non-empty. Abort the | ||
* handshake if the client doesn't send its certificate (can be empty). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dont love the "(can be empty)" and technically its redundant since i mention non-empty. Thoughts on if we should keep it or re-word it?
api/s2n.h
Outdated
* - Optional: Request the client's certificate and validate it. If no certificate is received then | ||
* no validation is performed. | ||
* - Required: Request the client's certificate and validate it. Abort the handshake if a client | ||
* certificate is not received. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: the spacing here is still inconsistent. I would either remove all of the newline indenting or fix this one.
* certificate is not received. | |
* certificate is not received. |
Description of changes:
s2n-tls has a concept of
s2n_cert_auth_type
which controls handshake behavior depending on the type of connection (server vs client). This behavior is complex and undocumented. This PR attempts to document the behavior.Callout:
The default behavior was recently changed in #4390
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.