You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementations of FakeKeystore will produce a generated.keystore that uses the proprietary JKS format (not even JKCES). Latest versions of keytool are already alerting about the fact:
Warning:
The JKS keystore uses a proprietary format. It is recommended
to migrate to PKCS12 which is an industry standard format using
"keytool -importkeystore -srckeystore generated.keystore \
-destkeystore generated.keystore -deststoretype pkcs12".
so FakeKeystore should produce PKCS12 keystores and be able to read both.
The text was updated successfully, but these errors were encountered:
The keyStores produced by FakeKeyStore should be usable as keystore or truststore. ATM ssl-config doesn't support PKCS12 as truststore due to the bug fixed in #92 .
Current implementations of
FakeKeystore
will produce agenerated.keystore
that uses the proprietaryJKS
format (not evenJKCES
). Latest versions ofkeytool
are already alerting about the fact:so
FakeKeystore
should produce PKCS12 keystores and be able to read both.The text was updated successfully, but these errors were encountered: