Move/Deprecate SunJce based CryptoCertificateProvider as separate module
bjakke opened this issue · 0 comments
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.