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

KeyShareEntry: include private key fields for KYBER #8196

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

SparkiDev
Copy link
Contributor

Description

Originallt HAVE_PQC and then changed to HAVE_FALCON and HAVE_DILITHIUM. The KEM PQC algorithm is actually KYBER.

Fixes zd#18923

Testing

./configure --enable-kyber --disable-dh
make

Checklist

  • added tests
  • updated/added doxygen
  • updated appropriate READMEs
  • Updated manual and documentation

Originallt HAVE_PQC and then changed to HAVE_FALCON and HAVE_DILITHIUM.
The KEM PQC algorithm is actually KYBER.
@SparkiDev SparkiDev assigned SparkiDev and wolfSSL-Bot and unassigned SparkiDev Nov 17, 2024
kp-thomas-yau added a commit to expressvpn/wolfssl-rs that referenced this pull request Nov 18, 2024
Use the official fix from WolfSSL PR: wolfSSL/wolfssl#8196 instead of our own implementation to enable private key fields in key share entry when we are using post-quantum KEM.
kp-thomas-yau added a commit to expressvpn/wolfssl-rs that referenced this pull request Nov 18, 2024
Use the official fix from WolfSSL PR: wolfSSL/wolfssl#8196 instead of our own implementation to enable private key fields in key share entry when we are using post-quantum KEM.
@dgarske dgarske merged commit c111bb8 into wolfSSL:master Nov 18, 2024
143 checks passed
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.

3 participants