Skip to content
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

Update to 1.3.56 #2

Merged
merged 286 commits into from
Feb 11, 2024
Merged

Update to 1.3.56 #2

merged 286 commits into from
Feb 11, 2024

Conversation

nickitat
Copy link
Member

No description provided.

lrstewart and others added 30 commits February 23, 2023 15:18
* Update s2n to latest PQ Hybrid TLS 1.3 Draft Specification
…load_cns (aws#3870)

* Revert defer_cleanup

* use ZERO_TO_DISABLE_DEFER_CLEANUP

* Add unit test

* Add second link

* Use defer cleanup for X509_NAME

* Break up test

* Call load cns multiple times

* Use default cert and check return values

* Avoid reassigning x509_name

* Move define pointer cleanup func into test
)

* tokio-s2n-tls: Enable access to the IO instance from TcpStream

* Rename io_* get_* for getting the inner stream

---------

Co-authored-by: Cameron Bytheway <[email protected]>
New usage is based on [the KEM API design document][1] and [header][2].
Now that we're on a stable KEM API, we remove the
S2N_AWSLC_KYBER_UNSTABLE build flag and always use the linked
libcrypto's Kyber implementation if available. This flag wasn't
previously specified in any of our CI scripts, meaning that
AWS-LC-backed kyber was previously uncovered in s2n's CI. This commit
ensures that coverage and updates the PQ KEM unit test to asserts that
if (non-FIPS) AWS-LC is used as the backing libcrypto, it has the new
Kyber 512 KEM API available.

[1]: https://github.com/aws/aws-lc/blob/main/crypto/kem/README.md
[2]: https://github.com/aws/aws-lc/blob/92c56fbc15f9bb43c4ff062c6c02f7991fd417f6/include/openssl/evp.h#L880

Check for other pre-processor symbol from AWS-LC
Mark-Simulacrum and others added 24 commits October 4, 2023 08:09
This is currently only supported for TLS 1.3 and is standard compliant,
using the TLS-Exporter function defined by RFC 8446:
https://www.rfc-editor.org/rfc/rfc8446#section-7.5
This commit shifts the TlsConnection trait to make it more generic. The
purpose of this is to allow more general usage of the TlsConnection
objects. In the future, "purpose-specific" logic will be implemented on
the Config type rather than the connection type.
@CLAassistant
Copy link

CLAassistant commented Jan 23, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 14 committers have signed the CLA.

✅ nickitat
✅ vitlibar
❌ toidiu
❌ lrstewart
❌ camshaft
❌ goatgoose
❌ jmayclin
❌ arielb1
❌ dougch
❌ Mark-Simulacrum
❌ WillChilds-Klein
❌ WesleyRosenblum
❌ maddeleine
❌ qinheping
You have signed the CLA already but the status is still pending? Let us recheck it.

@nickitat nickitat merged commit 8824ae2 into master Feb 11, 2024
0 of 2 checks passed
@nickitat nickitat deleted the upd_1.3.56 branch February 11, 2024 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.