Install Guide

Binary Installation for Android 19
RSA BSAFE SSL-J 6.2.6 Installation Guide
– To work with SSL-J configured as FIPS 140-2 compliant:
• Copy the following shared libraries to the platform-specific folder for the
shared native library files in the Android project at
/jniLibs/platform or /libs/platform:
• Copy the signature file,
libcryptocme.sig, to the
android-project /assets/platform directory.
For details about how to use Native configurations of SSL-J, see the API-specific
section Using Native Implementations in the RSA BSAFE SSL-J Developers
Guide.
7. To use the Crypto-J JsafeJCE API, dynamically register the Crypto-J JCE
provider, JsafeJCE:
a. Add the relevant jar files to the class path.
b. Create the provider programmatically using the following Java code:
// Create a Provider object
Provider jsafeProvider = new com.rsa.jsafe.provider.JsafeJCE();
// Add the Crypto-J JsafeJCE Provider to the current
// list of providers available on the system.
Security.insertProviderAt (jsafeProvider, 1);
Note: Unlike standard java, Android doesn't support static
registration of JCE providers, therefore the provider must be loaded
dynamically.
8. If required, set the following properties to configure SSL-J for FIPS 140-2
compliant operation:
• libccme_asym.so • libccme_ecc_accel_fips.so
• libccme_aux_entropy.so • libccme_ecc_accel_non_fips.so
• libccme_base.so • libccme_ecdrbg.so
• libccme_base_non_fips.so • libccme_error_info.so
• libccme_ecc.so • libcryptocme.so
• libccme_ecc_non_fips.so • libncm_fips140.so
Table 10 FIPS 140-2 Property Setting
Property Name Value
com.rsa.sslj.fips140initialmode FIPS140_MODE
1
1
The fips140initialmode value can be any of FIPS140_MODE, FIPS140_SSL_MODE, FIPS140_ECC_MODE,
FIPS140_SSL_ECC_MODE or NON_FIPS140_MODE
.
com.rsa.sslj.native.fips140.path
path
2
2
This property is set when using a Native configuration only. The path and filename can be an absolute path.