Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for using wolfJCE's
WKS
KeyStore type, which is in review on wolfcrypt-jni here (wolfSSL/wolfcrypt-jni#67). Specifically this PR:WKS
KeyStore type first before falling back to try and load others (BKS, JKS, etc).wolfjsse.keystore.type.required
) which can be used to restrict use of KeyStore type to the one set in this property. This can be used for example to help conform to wolfCrypt FIPS 140-2/3 crypto usage by setting to "WKS" when wolfJCE is also used and installed on the system.ClientJSSE.java
andServerJSSE.java
with new option to specify the KeyStore type (-ksformat
)ClientJSSE.java
to try and load system root/CA certs rather than using the provided KeyStore file (-sysca
)WolfSSLKeyManager.java
andWolfSSLTrustManager.java
around attempting to find and load system root/CA certs, making it easier to maintain in the future and adding support for WKS type stores.examples/provider/convert-to-wks.sh
)X509Certificate.getPublicKey()
to use JCE classes to generatePublicKey
, fixes edge test case when wolfJCE is installed alongside wolfJSSE.