Closed pauLee closed 4 years ago
That just means that the former default Java keystore formats JKS and JCEKS are not recommended anymore. This is not a KSE specific problem, you'll get the same warning if you create a JKS or JCEKS keystore with keytool.
You can change the keystore type to PKCS#12 in the Tools menu of KSE (i.e. the GUI equivalent of the command in the warning message):
As a side note: While it is true that JKS and JCEKS are not very secure formats for storing keys, they are still fine for storing certificates (as a truststore).
Thank you for the explanation!
I have thought about this a bit more and found something that I should change in KSE: When one creates a new keystore in KSE, JCEKS is the pre-selected keystore type. To reflect the changes in keytool, I'll make PKCS#12 the new default.
Thanks for taking the time to create this ticket!
Doing a list command for entries of a keystore-file, which is saved with Keystore-Explorer, results in a warning when using keytool on Linux:
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 /opt/xvm/... -destkeystore /opt/xvm/... -deststoretype pkcs12".
Environment