ECDSA Quantum-vulnerable 6 places See details
Classical signature algorithm through the JCA
`Signature.getInstance()` with a classical algorithm. The digest and the key algorithm are split out of the JCA name, so `SHA1withRSA` reports both the broken digest and the quantum-vulnerable key.
A quantum computer of sufficient size breaks this completely. It has to be replaced, not tuned. Broken by Shor's algorithm on a cryptographically relevant quantum computer.
What to do. ML-DSA-65 (FIPS 204). Where the verifier cannot be changed, sign twice and publish both signatures.
-
src/main/java/org/hyperledger/fabric_ca/sdk/helper/Config.java:90
defaultProperty(SIGNATURE_ALGORITHM, "SHA256withECDSA"); -
src/main/java/org/hyperledger/fabric/sdk/helper/Config.java:170
defaultProperty(SIGNATURE_ALGORITHM, "SHA256withECDSA"); -
src/main/java/org/hyperledger/fabric/sdk/security/certgen/TLSCertificateBuilder.java:53
private static final String defaultSignatureAlgorithm = "SHA256withECDSA"; -
src/main/java/org/hyperledger/fabric/sdk/security/certgen/TLSCertificateBuilder.java:67
signatureAlgorithm = defaultSignatureAlgorithm; -
src/main/java/org/hyperledger/fabric/sdk/security/certgen/TLSCertificateBuilder.java:125
ContentSigner signer = new JcaContentSignerBuilder(signatureAlgorithm) -
src/main/java/org/hyperledger/fabric/sdk/security/CryptoPrimitives.java:791
JcaContentSignerBuilder csBuilder = new JcaContentSignerBuilder("SHA256withECDSA");