logoalt Hacker News

zimmerfrei • yesterday at 7:07 PM • 1 reply • view on HN

The most likely explanation is that they generated the weak key externally, imported it into the HSM, generated the CSR from it, and finally had Root CA sign it.

A FIPS HSM does not forbid one to import keys into it.


Replies

cstdr • yesterday at 7:58 PM

But shouldn't such a HSM support key attestation (and the parent require such attestation)? Attestation would also track whether a key was imported or generated on the HSM, and of sufficient length.

➕ show 1 reply