Module Name
IBM® Crypto for C
Historical Reason
Moved to historical list due to sunsetting
Caveat
When operated in FIPS mode
Embodiment
Multi-chip standalone
Description
The IBM Crypto for C® v8.0 (ICC) cryptographic module is implemented in the C programming language. It is packaged as dynamic (shared) libraries usable by
applications written in a language that supports C language linking conventions (e.g. C, C++, Java, Assembler, etc.) for use on commercially available operating systems. The ICC allows these applications to access cryptographic functions using an Application Programming Interface (API) provided through an ICC import library and based on the API defined by the OpenSSL group.
Tested Configuration(s)
- AIX® 6.1 64-bit operating system (PowerPC 64)
- Microsoft Windows Server 2008® 32-bit operating system (x86-64)
- Microsoft Windows Server 2008® 64-bit operating system (x86-64)
- Red Hat Linux Enterprise Server 5 32-bit operating system (x86-64)
- Red Hat Linux Enterprise Server 5 64-bit operating system (x86-64, zSeries-64 and PowerPC-64) (single user mode)
- Solaris® 10 64-bit operating system (UltraSparc-64)
Approved Algorithms
| AES |
Certs. #1318, #1319, #1320, #1321, #1322, #1323, #1324, #1325, #1326, #1327, #1328, #1329, #1330 and #1331 |
| DRBG |
Certs. #34, #35, #36, #37, #38, #39, #40, #41, #42, #43, #44, #45, #46 and #47 |
| DSA |
Certs. #422, #423, #424, #425, #426, #427, #428, #429, #430, #431, #432, #433, #434 and #435 |
| ECDSA |
Certs. #157, #158, #159, #160, #161, #162, #163, #164, #165, #166, #167, #168, #169 and #170 |
| HMAC |
Certs. #766, #767, #768, #769, #770, #771, #772, #773, #774, #775, #776, #777, #778 and #779 |
| RSA |
Certs. #630, #631, #632, #633, #634, #635, #636, #637, #638, #639, #640, #641, #642 and #643 |
| SHS |
Certs. #1204, #1205, #1206, #1207, #1208, #1209, #1210, #1211, #1212, #1213, #1214, #1215, #1216 and #1217 |
| Triple-DES |
Certs. #917, #918, #919, #920, #921, #922, #923, #924, #925, #926, #927, #928, #929 and #930 |
Other Algorithms
RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD2; MD4; MD5; MDC2; RIPEMD; HMAC MD5; DES; CAST; Camellia; Blowfish; RC4; RC2
