Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

FakeKeystore should create PKCS12 format (read both JKS and PKCS12) #115

Open
ignasi35 opened this issue Sep 27, 2018 · 1 comment
Open

Comments

@ignasi35
Copy link
Contributor

ignasi35 commented Sep 27, 2018

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.

@ignasi35
Copy link
Contributor Author

This is blocked by #92.

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 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants