Getting started with RSA BSAFEÂ® Share For JAVAâ¢ Platform - EMC ...

More documents

Recommendations

Info

Upgrading: Sun’s JRE 6.0 to Share for Java Recommended Code Changes: SSLContext Issue: – SecureRandom parameters are sometimes passed to SSLContext.init. Sometimes this makes sense (for performance reasons, or because a special HSM SecureRandom object is being used), but usually, it is better to use the default. Review calls to the javax.net.ssl.SSLContext.init(KeyManager[] km, TrustManager[] tm, SecureRandom random) method. Passing null for the random parameter to the init method allows the JSSE provider to choose the best SecureRandom implementation. 12
Upgrading: Sun’s JRE 6.0 to Share for Java Recommended Code Changes: SSL Sockets Issue: – The TLS protocol version to support can be specified for a socket. Some applications may use this to limit protocol support to TLSv1, or maybe SSLv3 and TLSv1. This prevents applications from connecting with SSLv2. However, this also prevents Share for Java from using TLSv1.1 and TLSv1.2. Review calls to javax.net.ssl.SSLServerSocket.setEnabledProtocols and javax.net.ssl.SSLSocket.setEnabledProtocols Either remove these calls or add the values com.rsa.jsse.JsseProvider.TLS_V11 and com.rsa.jsse.JsseProvider.TLS_V12 to the array of algorithms supplied to the setEnabledProtocols method. 13
Page 1 and 2: RSA BSAFE ® Share for Java Platfor
Page 3 and 4: Objective As a result of this prese
Page 5 and 6: Upgrading Sun’s JRE 6.0 to Share
Page 7 and 8: Upgrading: Sun’s JRE 6.0 to Share
Page 9 and 10: Upgrading: Sun’s JRE 6.0 to Share
Page 11: Upgrading: Sun’s JRE 6.0 to Share
Page 15 and 16: Upgrading Share for Java to Crypto-
Page 17 and 18: Upgrading: Share to Crypto-J/Cert-J
Page 23: Thank you!

Getting started with RSA BSAFEÂ® Share For JAVAâ¢ Platform - EMC ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

Getting started with RSA BSAFEÂ® Share For JAVAâ¢ Platform - EMC ...