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

Allow requiring use of a post-quantum-safe KEM #5601

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

hlandau
Copy link

@hlandau hlandau commented Oct 24, 2024

This PR adds an experimental require_pq_kem boolean configuration option to the SPIRE agent and server which requires use of a post-quantum safe KEM (currently, the x25519Kyber768Draft00 KEM supported in Go 1.23).

This supercedes https://github.com/spiffe/spire/pull/5371.and implements the changes discussed there.

azdagron
azdagron previously approved these changes Nov 4, 2024
import (
"crypto/tls"

"github.com/hashicorp/go-hclog"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This package should leverage a logrus logger instead of hclog. The only code in the codebase that uses hclog is plugin code (due to tight coupling with hashicorp/go-plugin).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can leave this for now. If this feature becomes non-experimental at some point, we'll likely be passing this configuration to plugins via core configuration and can revisit this then.

@azdagron
Copy link
Member

azdagron commented Nov 4, 2024

Thanks for this, @hlandau. Would you mind merging in the latest main and fixing up the conflict?

azdagron
azdagron previously approved these changes Nov 6, 2024
@hlandau
Copy link
Author

hlandau commented Nov 7, 2024

@azdagron Rebased.

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.

2 participants