Skip to content

Use wolfCrypt SSHv2 KDF#729

Merged
dgarske merged 1 commit intowolfSSL:masterfrom
ejohnstown:new-kdf
Jul 30, 2024
Merged

Use wolfCrypt SSHv2 KDF#729
dgarske merged 1 commit intowolfSSL:masterfrom
ejohnstown:new-kdf

Conversation

@ejohnstown
Copy link
Copy Markdown
Contributor

@ejohnstown ejohnstown commented Jul 23, 2024

Switching to use the new SSH-KDF function in wolfCrypt. Note, this only works in FIPS builds and/or when Kyber isn't used.

@ejohnstown ejohnstown marked this pull request as draft July 26, 2024 15:29
@ejohnstown ejohnstown force-pushed the new-kdf branch 4 times, most recently from 5b795dc to 86ce2bd Compare July 29, 2024 23:39
@ejohnstown ejohnstown marked this pull request as ready for review July 29, 2024 23:47
@ejohnstown ejohnstown requested a review from dgarske July 29, 2024 23:48
Comment thread src/internal.c Outdated
#include <wolfssl/wolfcrypt/ecc.h>
#include <wolfssl/wolfcrypt/hmac.h>
#include <wolfssl/wolfcrypt/signature.h>
#include <wolfssl/wolfcrypt/kdf.h>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Was this header always available? If not maybe do a version macro to support older wolfSSL releases? LIBWOLFSSL_VERSION_HEX >= WOLFSSL_V5_7_2?

1. Switching to use the new SSH-KDF function in wolfCrypt when the
   correct version of wolfSSL (v5.0.0 at a minimum) is used, when
   certified version of wolfCrypt is used or Kyber is disabled.
2. Add WOLFSSL_WOLFSSH to the wolfSSL user_settings files for the Zephyr
   testing.
@ejohnstown ejohnstown removed their assignment Jul 30, 2024
@dgarske dgarske merged commit 40aabc2 into wolfSSL:master Jul 30, 2024
@ejohnstown ejohnstown deleted the new-kdf branch July 30, 2024 16:47
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