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
However, at least as of 82e3b99, The change is only effective when the workspace is created fresh, i.e. when the shipped 2018 keystore is used. Then, it seems the format is saved to disk in the sun format. as of 280dcf8 only an unrelated error is thrown:
The text was updated successfully, but these errors were encountered:
Keystore loading and item retrieval behavior is subject to the global static
java.security.Security
policy, which we set in https://github.com/jcryptool/core/blob/develop/de.flexiprovider/src/de/flexiprovider/FlexiProviderController.javaThe keystore file from 2018 has beein reinstated (in a non-develop branch!) here: 0e5b753
It looks like TLS is only working when sun providers have preference, while our keystore files only work when with flexiprovider Providers have preference. The branch
keystore_provider_experiment
has these changes: https://github.com/jcryptool/core/compare/keystore_provider_experimentHowever, at least as of 82e3b99, The change is only effective when the workspace is created fresh, i.e. when the shipped 2018 keystore is used. Then, it seems the format is saved to disk in the sun format.as of 280dcf8 only an unrelated error is thrown:The text was updated successfully, but these errors were encountered: