CRYPTREC
- 4 min read
- 5 chapters
Related on Lably
Through European Union and Government
Comparison with NESSIE
There is some overlap, and some conflict, between the NESSIE selections and the CRYPTREC draft recommendations. Both efforts include some of the best cryptographers in the world therefore conflicts in their selections and recommendations should be examined with care. For instance, CRYPTREC recommends several 64 bit block ciphers while NESSIE selected none, but CRYPTREC was obliged by its terms of reference to take into account existing standards and practices, while NESSIE was not. Similar differences in terms of reference account for CRYPTREC recommending at least one stream cipher, RC4, while the NESSIE report specifically said that it was notable that they had not selected any of those considered. RC4 is widely used in the SSL/TLS protocols; nevertheless, CRYPTREC recommended that it only be used with 128-bit keys. Essentially the same consideration led to CRYPTREC's inclusion of 160-bit message digest algorithms, despite their suggestion that they be avoided in new system designs. Also, CRYPTREC was unusually careful to examine variants and modifications of the techniques, or at least to discuss their care in doing so; this resulted in particularly detailed recommendations regarding them.
Sign in to keep reading
4 more chapters are free with a Lably account.
Background and sponsors
CRYPTREC includes members from Japanese academia, industry, and government. It was started in May 2000 by combining efforts from several agencies who were investigating methods and techniques for implementing 'e-Government' in Japan. Presently, it is sponsored by
- the Ministry of Economy Trade and Industry,
- the Ministry of Public Management, Home Affairs and Post and Telecommunications,
- the Telecommunications Advancement Organization, and
- the Information-Technology Promotion Agency.
Responsibilities
It is also the organization that provides technical evaluation and recommendations concerning regulations that implement Japanese laws. Examples include the Electronic Signatures and Certification Services (Law 102 of FY2000, taking effect as from April 2001), the Basic Law on the Formulation of an Advanced Information and Telecommunications Network Society of 2000 (Law 144 of FY2000), and the Public Individual Certification Law of December 2002. Furthermore, CRYPTEC has responsibilities with regard to the Japanese contribution to the ISO/IEC JTC 1/SC27 standardization effort.
Selection
In the first release in 2003, many Japanese ciphers were selected for the "e-Government Recommended Ciphers List": CIPHERUNICORN-E (NEC), Hierocrypt-L1 (Toshiba), and MISTY1 (Mitsubishi Electric) as 64 bit block ciphers, Camellia (Nippon Telegraph and Telephone, Mitsubishi Electric), CIPHERUNICORN-A (NEC), Hierocrypt-3 (Toshiba), and SC2000 (Fujitsu) as 128 bit block ciphers, and finally MUGI and MULTI-S01 (Hitachi) as stream ciphers.
In the revised release of 2013, the list was divided into three: "e-Government Recommended Ciphers List", "Candidate Recommended Ciphers List", and "Monitored Ciphers List". Most of the Japanese ciphers listed in the previous list (except for Camellia) have moved from the "Recommended Ciphers List" to the "Candidate Recommended Ciphers List". There were several new proposals, such as CLEFIA (Sony) as a 128 bit block cipher as well as KCipher-2 (KDDI) and Enocoro-128v2 (Hitachi) as stream ciphers. However, only KCipher-2 has been listed on the "e-Government Recommended Ciphers List". The reason why most Japanese ciphers have not been selected as "Recommended Ciphers" is not that these ciphers are necessarily unsafe, but that these ciphers are not widely used in commercial products, open-source projects, governmental systems, or international standards. There is the possibility that ciphers listed on "Candidate Recommended Ciphers List" will be moved to the "e-Government Recommended Ciphers List" when they are utilized more widely.
In addition, 128 bit RC4 and SHA-1 are listed on "Monitored Ciphers List". These are unsafe and only permitted to remain compatible with old systems.
After the revision in 2013, there are several updates such as addition of ChaCha20-Poly1305, EdDSA and SHA-3, move of Triple DES to Monitored list, and deletion of RC4, etc.
CRYPTREC Ciphers List
As of March 2023
e-Government Recommended Ciphers List
- Public key ciphers
- Symmetric key ciphers
- Hash functions
- Modes of operation
- Message authentication codes
- CMAC
- HMAC
- Authenticated encryption
- ChaCha20-Poly1305
- Entity authentication
- ISO/IEC 9798-2
- ISO/IEC 9798-3
- ISO/IEC 9798-4
Candidate Recommended Ciphers List
- Public key ciphers
- Signature
- N/A
- Confidentiality
- N/A
- Key exchange
- PSEC-KEM
- Signature
- Symmetric key ciphers
- 64-bit block ciphers
- CIPHERUNICORN-E
- Hierocrypt-L1
- MISTY1
- 128-bit block ciphers
- CIPHERUNICORN-A
- CLEFIA
- Hierocrypt-3
- Stream ciphers
- Enocoro-128v2
- MUGI
- MULTI-S01
- 64-bit block ciphers
- Hash functions
- N/A
- Modes of operation
- Encryption modes
- N/A
- Authenticated encryption modes
- N/A
- Encryption modes
- Message authentication codes
- PC-MAC-AES
- Authenticated encryption
- N/A
- Entity authentication
- N/A
Monitored Ciphers List
- Public key ciphers
- Signature
- N/A
- Confidentiality
- Key exchange
- N/A
- Signature
- Symmetric key ciphers
- 64-bit block ciphers
- 3-key Triple DES
- 128-bit block ciphers
- N/A
- Stream ciphers
- N/A
- 64-bit block ciphers
- Hash functions
- RIPEMD-160
- SHA-1
- Modes of operation
- Encryption modes
- N/A
- Authenticated encryption modes
- N/A
- Encryption modes
- Message authentication codes
- Authenticated encryption
- N/A
- Entity authentication
- N/A