Skip to content

fips-baseline: re-add SSHKDF to default and FIPS providers#396

Open
ColtonWilley wants to merge 1 commit intomasterfrom
wp_sshkdf_fips_baseline
Open

fips-baseline: re-add SSHKDF to default and FIPS providers#396
ColtonWilley wants to merge 1 commit intomasterfrom
wp_sshkdf_fips_baseline

Conversation

@ColtonWilley
Copy link
Copy Markdown
Contributor

Follow-up to #382. The fips-baseline patches strip SSHKDF from the default and FIPS provider tables, but it's FIPS-compliant (SHA-2 only) and stock OpenSSL 3 ships it in both. Restoring it across the four defltprov and five fipsprov variants so applications built against fips-baseline OpenSSL can still EVP_KDF_fetch("SSHKDF") -- specifically RHEL openssh, which goes through that fetch on every key exchange via Patch964.

SSHKDF (RFC 4253) was stripped from both the default and FIPS providers by
the fips-baseline patches, but the KDF is FIPS-compliant: it derives keys
using FIPS-approved hash functions (SHA-2 family). Stock OpenSSL 3 ships it
in both providers. wolfProvider implements it, and RHEL's openssh-kdf patch
(Patch964) routes every SSH key exchange through EVP_KDF_fetch("SSHKDF") —
so stripping it breaks RHEL-patched openssh entirely under the baseline.

Re-add the entry across all 4 defltprov and 5 fipsprov variant files so
callers using the fips-baseline build can fetch SSHKDF the same as they
would from stock OpenSSL.
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.

1 participant