-
Notifications
You must be signed in to change notification settings - Fork 2k
Security provider support missing from legacy releases >22.0.0 #3994
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
Comments
I don't think this is on purpose, I think that we need to cherry-pick this into the release-23-legacy branch. Release 22.0.0 was accidentally cut on the wrong branch, that's why it is in that release. If you send a cherry-pic PR to the legacy branches, I can cut a new release(s) |
Ok, I'll go ahead and do that, thanks. Will that code be available in future legacy branch releases as well? (release-24-legacy and so on) |
If you cherry-pick it into the master-java8 branch it should also go forward, though it's not clear how long we are going to maintain those branches. Java8 is pretty much 100% deprecated. |
I haven't had any time to approach this, is there any way someone can do the small cherry pick of the security providers onto release-legacy-22,23, and master-java8 branches? |
Hi All,
I am trying to use kubernetes-client java on a FIPS enabled machine using the bouncy castle FIPS libraries. Commit #3590 allowed for bouncy castle FIPS support and loading of security providers but only seems to be included in release 22.0.0-legacy, and not 22.0.1-legacy or 23.0.0-legacy. Is this on purpose? I'm unable to use version 22.0.0-legacy because of its incompatibility with Java 8.
Client Version
23.0.0-legacy
Java Version
Java 8
Server:
OS: Linux
The text was updated successfully, but these errors were encountered: