-
Notifications
You must be signed in to change notification settings - Fork 745
docs(bindings): expand readme for s2n-tls #5505
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
base: main
Are you sure you want to change the base?
Conversation
| - TLS 1.3 stateless session resumption | ||
| - Early Data |
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.
Do we actually have bindings for early data?
|
|
||
| ## Features | ||
| - SSLv3 - TLS 1.3 |
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.
If we're listing SSLv3... should we list renegotiation too? 😬
|
|
||
| ## Features |
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.
We might not be perfect about updating this, and it's probably not exhaustive now. So maybe instead:
| ## Features | |
| ## Features | |
| Available features include: |
|
|
||
| ## Cryptography Provider | ||
|
|
||
| By default, the s2n-tls bindings will rely on [aws-lc-rs](https://crates.io/crates/aws-lc-rs) for cryptography. To use a FIPS validated libcrypto, customers can enable the `fips` feature flag in `s2n-tls`. This enables the `fips` feature in the underlying AWS-LC libcrypto. |
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.
Should we also mention that technically you can make it build with a different libcrypto if you really try?
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.
If we allow building with a different libcrypto, can we also include documentation about how to do it?
Description of changes:
Our previous README was very sparse. This new readme mentions some of the features, and calls out the libcrypto configuration.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.