Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Move/Deprecate SunJce based CryptoCertificateProvider as separate module #164

Closed
bjakke opened this issue Sep 19, 2018 · 0 comments
Closed
Milestone

Comments

@bjakke
Copy link
Contributor

bjakke commented Sep 19, 2018

Currently there is a last-effort-fallback classes SunJceCertificateProvider and SunJceCryptoProvider that needs to be specifically enabled for CryptoUtil if BouncyCastle/SpongyCastle cannot be used. These are not able to cover all use cases (#7) and do not work in java 9+ as private apis are no longer accessible. In practice for the proper functionality applications need to anyway use BouncyCastle/SpongyCastle.

It should be moved to a separate module at least. This also allows changing the signature for the animal-sniffer-maven-plugin to enforce that no private api is used. It would also serve as a possible starting point for a custom provider.

Java 8/11 might provide alternative ways to do the equivalent operations, so it might be possible to create separate modules or documentation for those.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant