Fixes and Features in CommonCryptoLib
Fixes and Features in CommonCryptoLib
CommonCryptoLib 8.4.31 contains several new features and improvements (see Solution section) and fixes for the following problems.
You are using CommonCryptoLib 8.4.30 or earlier and detect one of the following issues:
- You detect an increasing memory consumption of one or more work processes.
- CommonCryptoLib may behave unstable or crash if the calling application runs into an out-of-memory situation.
- PSE- and PKCS#12 files created/exported by CommonCryptoLib get unrestrictive file permissions on UNIX/Linux operating systems.
- You encounter an error like “Cannot open PSE” when using a specific PSE. Traces or error messages show “Division by zero” or “A function called indirectly got an invalid parameter”.
- You miss RIPEMD128 hash algorithm for SSF signing.
- The ABAP report RPUSVHD0 states that the PSE file could not be read. The RPUSVHD0 test report shows error “SSF kernel error: Invalid parameter”. A check of the affected PSE with “sapgenpse get_my_name” indicates the error “Couldn’t open PSE … (Missing PIN/Passphrase, no credentials found)”.
- You are using sapgenpse import_p12 to import a PKCS#12 file and see an unexpected key usage displayed.
- SAP Webdispatcher is unable to establish SSL connections. dev_disp log file shows errors “PSE …: unable to use!” and “Wrong PIN or PSE corrupted”. This error may not only occur in Webdispatcher scenarios.
- You try to create a certificate request in transaction STRUST, it fails but no error is displayed. In trace dev_w* an error like
“*** ERROR => == krn_Ssf_GetCertificateRequest()==13 (SSF_API_UNKNOWN_SECTK_ERROR)” is dumped.
CommonCryptoLib, SAPCRYPTOLIB, SNC, SSF, SSL, SLS, RSA, AES-NI, TLS, STRUST
Reason and Prerequisites
CommonCryptoLib 8.4.30 or earlier has programming errors causing the described issue.
- There were two functions which did not correctly release the allocated memory.
- If an applications is not able to allocate new memory for an operation, this should results in an error. Depending where the allocation failed, older CommonCryptoLib version may have crashed or returned a wrong error.
- PSE- or PKCS#12-files created/exported via CommonCryptoLib functions (also when using sapgenpse) written with file permissions rw-r–r– (644) on UNIX/Linux systems.
- The faulting PSE was created by importing a RSA key with a public exponent different from 65537. The problem may be caused by importing a PKCS#8 or PKCS#12 file created by 3rd party software, or after replacing SAPCRYPTOLIB 5.5.5 by CommonCryptoLib. You may check an affected PSE with “sapgenpse get_my_name” command.
- RIPEMD128 was not enabled for use with SSF.
- The CommonCryptoLib function which is used by report RPUSVKD0 (and probably others) to create the PSE credentials produce a corrupted credential file (cred_v2).
- The import_p12 function does not know the key usages dataEncipherment and cRLSign and therefore they are incorrectly displayed.
- The problem is caused by a X.509 Distinguished Name consisting of 19 or more components (CN=…, CN=…, OU=…, O=…, …). “sapgenpse get_my_name|seclogin” can be used to check. In case the problem exists with the PSE, get_my_name does not show the Distinguished Name, and seclogin crashes.
- You have upgraded from SAPCRYPTOLIB 5.5.5 to COMMONCRYPTOLIB 8 Patch 8.4.30 or earlier. The PSE used to create the certificate request contains 8 or more certificates in the list of trusted certificates.
Download CommonCryptoLib 8.4.31 (or higher) and install/update it on the affected system. The following fixes/improvements come with this patch:
- Two memory leaks fixed.
- Improved memory handling (especially handling out of memory situations).
- More secure file permissions for PSE/PKCS#12 files on UNIX/Linux systems rw——- (600).
- Fixed support of RSA keys using a public exponent different from 65537.
- RIPEMD128 for SSF activated.
- The affected function is fixed, cred_v2 is correctly created now.
- import_p12 function fixed.
- Handling of PSEs with long X.509 Distinguished Names fixed.
- Create certificate request function has been fixed
TLS 1.1/1.2 Support
CommonCryptoLib 8.4.31 supports SSL connections using TLS 1.1 and TLS 1.2 protocol versions.
On NetWeaver AS ABAP/AS JAVA or SAP HANA XS systems, two new protocol flags are supported for use within profile parameter ssl/ciphersuites:
- 256 for TLS 1.1
- 512 for TLS 1.2
For a detailed description of protocol version configuration, please refer to section 7 of SAP Note 510007; configurability of protocol versions requires a minimum Kernel patch level as described in SAP Note 1433874 (from 2010–all moderately recent Kernel software should have this configurability).
As a rule of thumb, the use of the following profile parameter settings are currently recommended:
and in case that you were using the special client settings for blind sending of a client certificate in response to a malformed CertificateRequest handshake message, as described in SAP Note 1841573 (issue 2), then you should continue using this profile parameter setting for the client side:
The settings suggested above can be used with all crypto library versions (whereas using the explicit flags for TLSv1.1 and TLSv1.2 is limited to CommonCryptoLib 8.4.31 and successors). The first profile parameter value disables SSLv3 for the server-side and enables TLSv1.0, TLSv1.1 and TLSv1.2 plus CLIENT-HELLO 2.0 interop, and the second parameter configures SSLv3 & TLSv1.0 on the client side, which is the most interoperable client configuration, and safe for use by purely programmatic TLS clients.
Please note that – for compatibility and interoperability reasons – TLS 1.0 and TLS1.1 will currently be automatically enabled when TLS 1.1 or TLS 1.2 are enabled/requested.
The algorithms for RSA keys were optimized for speed. This affects signature, encryption, and authentication operations for SSL, GSS (SNC), and SSF as long as an RSA key is used.
The AES128/192/256 algorithms were optimized for speed. This affects data encryption for SSL/TLS and GSS (SNC) connections.
On CPUs with AES-NI extension (Intel/AMD x86 architecture), additional speed optimization has been achieved.
RSA-PSS for Secure Login Server with HSM
When a Secure Login Server is configured to use a hardware security module as User CA (External CA), it was not possible to use RSA-PSS based signature algorithms. Now the following algorithms are supported:
- SHA-1 with RSA-PSS (sha1WithRSAPSS)
- SHA-256 with RSA-PSS (sha256WithRSAPSS)
- SHA-512 with RSA-PSS (sha512WithRSAPSS)
Secure Login Server 2.0 SP03 Patch Level 1 or higher is required to support these algorithms.
|Software Component||From||To||And Subsequent|
More[ 20 / 45 ]
|Software Component||Support Package||Patch Level||Download|
|SAP KERNEL 7.20 32-BIT||SP713||713|
|SAP KERNEL 7.20 32-BIT UNICODE||SP713||713|
|SAP KERNEL 7.20 64-BIT||SP713||713|
|SAP KERNEL 7.20 64-BIT UNICODE||SP713||713|
|SAP KERNEL 7.20 EXT 32-BIT||SP713||713|
|SAP KERNEL 7.20 EXT 32-BIT UC||SP713||713|
|SAP KERNEL 7.20 EXT 64-BIT||SP713||713|
|SAP KERNEL 7.20 EXT 64-BIT UC||SP713||713|
|SAP KERNEL 7.21 32-BIT||SP333||333|
|SAP KERNEL 7.21 32-BIT UNICODE||SP333||333|
|SAP KERNEL 7.21 64-BIT||SP333||333|
|SAP KERNEL 7.21 64-BIT UNICODE||SP333||333|
|SAP KERNEL 7.38 64-BIT||SP069||69|
|SAP KERNEL 7.38 64-BIT||SP070||70|
|SAP KERNEL 7.38 64-BIT UNICODE||SP069||69|
|SAP KERNEL 7.38 64-BIT UNICODE||SP070||70|
|SAP KERNEL 7.41 64-BIT||SP114||114|
|SAP KERNEL 7.41 64-BIT UNICODE||SP114||114|
More[ 20 / 22 ]
|Other Components||BC-CST-IC Internet Communication Manager|