JiriOndrusek opened a new pull request, #6241: URL: https://github.com/apache/camel-quarkus/pull/6241
fixes https://github.com/apache/camel-quarkus/issues/6088 Crypto component was split into `crypto` and `crypto-pgp` to support FIPS. See the [commit](https://github.com/apache/camel/pull/14651/commits/2161144a8c06b23732aa8947e02e738a251bdef8). (this is the reason of why this PR is opened against `camel-main`) - `crypto-pgp` is not registering BC as a provider; component contains only PGPDataFormat - `crypto` contains all other (CryptoDataFormat, components) **How to run `crypto` on FIPS** the BC dependency has to be excluded and BCFIPS added (or another BC implementation for FIPS) . **Limitation:** Because of the BCFIPS, it is not possible to use crypto and crypto-pgp together on FIPS system (if BCFIPS is utilized) This PR contains: - new extension based on `crypto-pgp` component (uses BC). The component and all tests are extracted from the `crypto` component. All tests work on FIPS system. - fixes in bouncycastle-support to work correctly on FIPS system - added `fips` profile in crypto integration test module, to allow execution on FIPS systems - some *.adoc addition for FIPS in crypto and crypto-pgp etensions - it is not possible to utilize `certificate-generator-support` because the tests require `DES` and the `certificate-generator-support` uses `RSA`. <!-- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
