davsclaus opened a new pull request, #24653: URL: https://github.com/apache/camel/pull/24653
## Summary _Claude Code on behalf of davsclaus_ Bouncy Castle 1.85 removed the pre-standardization PQC algorithm names (DILITHIUM, KYBER, SPHINCSPLUS) from the BCPQC provider. This PR adapts camel-pqc to use the NIST standardized names: - **DILITHIUM** → `ML-DSA` (BC provider) — FIPS 204 - **KYBER** → `ML-KEM` (BC provider) — FIPS 203 - **SPHINCSPLUS** → `SLH-DSA` (BC provider) — FIPS 205 The Camel enum constants (`signatureAlgorithm=DILITHIUM`, `keyEncapsulationAlgorithm=KYBER`, etc.) are preserved unchanged for backward compatibility — existing routes continue to work transparently. Changes: - Updated `PQCSignatureAlgorithms.DILITHIUM` and `.SPHINCSPLUS` to use new JCA names and BC provider - Updated `PQCKeyEncapsulationAlgorithms.KYBER` to use new JCA name and BC provider - Updated default parameter specs from old BC classes (`DilithiumParameterSpec`, `KyberParameterSpec`, `SPHINCSPlusParameterSpec`) to standardized ones (`MLDSAParameterSpec`, `MLKEMParameterSpec`, `SLHDSAParameterSpec`) - Updated all lifecycle managers (File, AWS, Hashicorp) and crypto material classes - Updated all tests This is a companion to PR #24648 (Bouncy Castle 1.84 → 1.85 version bump). ## Test plan - [x] All 168 camel-pqc tests pass (including `PQCEndToEndIntegrationTest` which was failing) - [x] Code compiles and formats correctly 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
