Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[openpgp] Do not put the BouncyCastleProvider at first position
This causes java.security.InvalidKeyException: cannot identify XDH private key on Java 11 or higher. See also - bcgit/bc-java#620 - bcgit/bc-java#589 - corretto/corretto-11#168 - https://bugs.openjdk.java.net/browse/JDK-8171279
- Loading branch information
9261d64
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I just wanted to mention that this issue was fixed in Bouncy Castle 1.66, which is older than the version of JDK11 that added support for x448 and x25519. As long as people keep BC up to date, there is no problem with JDK11
9261d64
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I ran into it also with bc 1.68 on Java 11. But hat doesn't matter: Smack as library should not modify the SecurityProvider in that way. Hence this commit.