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

More documents

Recommendations

Info

Upgrading: Share to Crypto-J/Cert-J/SSL-J Native Crypto To use Native Crypto: – Ensure the platform specific shared library is in the Java library path or the system library path. – On Windows: • Copy cryptoj\prebuilt\cryptoc\win32\lib\jsafe.dll to C:\WINDOWS\system32 – Native algorithms will be used if they are available. 20
Upgrading: Share to Crypto-J/Cert-J/SSL-J PKCS #11 To use PKCS #11 Crypto: – Ensure the platform specific shared libraries are in the Java library path or the system library path, and that the PKCS #11 driver is in the system library path. – On Windows: • Copy cryptoj\prebuilt\cryptoc\win32\lib\jsafe.dll and cryptoj\prebuilt\cryptoc\win32\lib\jsafepkcs11.dll to C:\WINDOWS\system32 – Use PKCS #11 algorithms names: • KeyPairGenerator: DSAWithPKCS11, RSAWithPKCS11. • Cipher: RSAWithPKCS11. • Signature: SHA1withRSAandPKCS11, NONEwithRSAandPKCS11, SHA1withDSAandPKCS11. 21
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 15 and 16: Upgrading Share for Java to Crypto-
Page 17 and 18: Upgrading: Share to Crypto-J/Cert-J
Page 19: 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 ...