JiriOndrusek opened a new pull request, #8507: URL: https://github.com/apache/camel-quarkus/pull/8507
related to https://github.com/apache/camel-quarkus/issues/8497 Add Post-Quantum Cryptography (PQC) hybrid approach test coverage for HTTP component Implements hybrid RSA+ML-DSA certificate validation for HTTP component using BouncyCastle JSSE provider. Adds new pqc-certificate-generator test support module for generating hybrid certificates following [BC Almanac Chimera](https://downloads.bouncycastle.org/java/docs/PQC-Almanac.pdf) pattern (page 6). Key changes: - New test infrastructure: integration-tests-support/pqc-certificate-generator module - Hybrid certificate generation using NIST-standardized ML-DSA algorithms (FIPS 204) - HTTP integration test with nginx serving hybrid certificates - Custom HybridCertificateTrustManager validating both RSA and ML-DSA signatures - Standard TLS 1.3 handshake with application-level PQC validation Technical approach: - Uses standard TLS with hybrid X.509 certificates (RSA + ML-DSA keys via extensions) - Compatible with any TLS 1.3 server (no OQS/protocol modifications needed) - Client-side validation via @PQCCertificates JUnit extension <!-- Uncomment and fill this section if your PR is not trivial [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html --> -- 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]
