kubernetes-client
kubernetes-client copied to clipboard
FIPS support without BouncyCastle
Is your enhancement related to a problem? Please describe
Currently, in order to use EC keys, the code checks for the BouncyCastle provider. Because of redistribution limitations with the BC FIPS jars, the client should also allow using a JDK configured to use the NSS-backed security provider (this, for example, is automatically enabled on RHEL/CentOS in FIPS mode).
Describe the solution you'd like
The code should test to see if EC keys can be handled directly by the JDK before resorting to other strategies (e.g. BouncyCastle).
Describe alternatives you've considered
No response
Additional context
No response
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!
https://github.com/fabric8io/kubernetes-client/pull/2788/files#r571887528
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!