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

Implement TLS 1.3 key schedule using crypto/hkdf #1472

Open
wants to merge 2 commits into
base: microsoft/main
Choose a base branch
from

Conversation

qmuntal
Copy link
Member

@qmuntal qmuntal commented Jan 9, 2025

TLS 1.3 Key Schedule is normally not part of the FIPS boundary, but upstream Go decided to include it in the FIPS boundary to facilitate the FIPS 140-3 certification process.

The problem is that crypto/internal/fips140/tls13 uses crypto/internal/fips140/hkdf, which can't be patched to use other backends.

To solve this problem, we created this package, which is a direct copy of crypto/internal/fips140/tls13, but uses crypto/hkdf instead of crypto/internal/fips140/hkdf.

I tried hard to move the tls13 outside of the FIPS boundary without luck: https://go-review.googlesource.com/c/go/+/626836/comments/6e8e9eee_7a8fbce3.

Fixes #1470.

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.

Implement TLS 1.3 KDF using the crypto backends
2 participants