I’ve tasked myself with getting one of our most used vendor apps up to compliance with our security audits. It’s not as easy as I’d hoped. Especially seeing as I seem to have run beyond the encryption export limitations Java distribute.
One of the products uses JDBC to connect to a Microsoft SQL server which is hardened and only supports a limited set of high grade encryption ciphers. This caused me to see connection failures with exception messages such as “failed to generate DH keypair” and “RSA premaster secret error”.
Then I discovered the Bouncy Castle.
As Java security providers seem to have limitations in regard to key sizes I had to add another security provider that is documented here:
In order to enable this feature I added the “BouncyCastle” JCE by:
- Downloading the Bouncy Castle JCE from https://www.bouncycastle.org/latest_releases.html
- Copy the downloaded .jar file to
- Edit the
%JAVA_HOME%\lib\security\java.securityfile and add the following line into the list of providers replacing 11 with whatever the last number in the existing list:
As I encountered Bouncy Castle I also came across Java policy files that unrestrict what algorithms can be used (it does not add the ciphers, just unrestricts their use if you have them). I’m unsure if these policy files are necessary in my instance, but I installed them never the less.
It’s a very simple install. Simply download and extract the files. Copy the .jar files to
%JAVA_HOME%/lib/security overwriting the existing files.
Now I can successfully connect to the SQL server.
Note: You may have to add the CA certificate to your Java -trustcacerts that matches your SQL servers certificate signing CA.