The SM4 Block Cipher Algorithm And Its Modes Of Operations
draftribosecfrgsm400
The information below is for an old version of the document.
Document  Type 
This is an older version of an InternetDraft whose latest revision state is "Expired".



Authors  Ronald Henry Tse , Wong Wai Kit  
Last updated  20170912  
RFC stream  (None)  
Formats  
Stream  Stream state  (No stream defined)  
Consensus boilerplate  Unknown  
RFC Editor Note  (None)  
IESG  IESG state  ID Exists  
Telechat date  (None)  
Responsible AD  (None)  
Send notices to  (None) 
draftribosecfrgsm400
Crypto Forum Research Group R. Tse InternetDraft Ribose Intended status: Informational W. Wong Expires: March 16, 2018 Hang Seng Management College September 12, 2017 The SM4 Block Cipher Algorithm And Its Modes Of Operations draftribosecfrgsm400 Abstract This document describes the SM4 symmetric blockcipher algorithm published as GB/T 329072016 by the Organization of State Commercial Administration of China (OSCCA). This document is a product of the Crypto Forum Research Group (CFRG). Status of This Memo This InternetDraft is submitted in full conformance with the provisions of BCP 78 and BCP 79. InternetDrafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as InternetDrafts. The list of current Internet Drafts is at https://datatracker.ietf.org/drafts/current/. InternetDrafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use InternetDrafts as reference material or to cite them other than as "work in progress." This InternetDraft will expire on March 16, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/licenseinfo) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Tse & Wong Expires March 16, 2018 [Page 1] InternetDraft September 2017 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. History . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3. Applications . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Cryptanalysis . . . . . . . . . . . . . . . . . . . . . . 5 2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 5 3. Symbols And Abbreviations . . . . . . . . . . . . . . . . . . 6 4. Compute Structure . . . . . . . . . . . . . . . . . . . . . . 6 5. Key And Key Parameters . . . . . . . . . . . . . . . . . . . 6 6. Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. Round Function F . . . . . . . . . . . . . . . . . . . . 7 6.2. Permutation T and T' . . . . . . . . . . . . . . . . . . 7 6.2.1. Nonlinear Transformation tau . . . . . . . . . . . . 7 6.2.2. Linear Transformation L and L' . . . . . . . . . . . 8 6.2.3. Sbox S . . . . . . . . . . . . . . . . . . . . . . . 8 7. Calculations . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1. Encryption . . . . . . . . . . . . . . . . . . . . . . . 9 7.2. Decryption . . . . . . . . . . . . . . . . . . . . . . . 9 7.3. Key Schedule . . . . . . . . . . . . . . . . . . . . . . 9 7.3.1. System Parameter FK . . . . . . . . . . . . . . . . . 10 7.3.2. Constant Parameter CK . . . . . . . . . . . . . . . . 10 8. Modes of Operation . . . . . . . . . . . . . . . . . . . . . 11 8.1. Variables And Primitives . . . . . . . . . . . . . . . . 11 8.2. Initialization Vectors . . . . . . . . . . . . . . . . . 12 8.3. SM4ECB . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.3.1. SM4ECB Encryption . . . . . . . . . . . . . . . . . 12 8.3.2. SM4ECB Decryption . . . . . . . . . . . . . . . . . 13 8.4. SM4CBC . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.4.1. SM4CBC Encryption . . . . . . . . . . . . . . . . . 13 8.4.2. SM4CBC Decryption . . . . . . . . . . . . . . . . . 14 8.5. SM4CFB . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.5.1. SM4CFB Variants . . . . . . . . . . . . . . . . . . 15 8.5.2. SM4CFB Encryption . . . . . . . . . . . . . . . . . 15 8.5.3. SM4CFB Decryption . . . . . . . . . . . . . . . . . 16 8.6. SM4OFB . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.6.1. SM4OFB Encryption . . . . . . . . . . . . . . . . . 17 8.6.2. SM4OFB Decryption . . . . . . . . . . . . . . . . . 18 8.7. SM4CTR . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.7.1. SM4CTR Encryption . . . . . . . . . . . . . . . . . 19 8.7.2. SM4CTR Encryption . . . . . . . . . . . . . . . . . 20 9. Object Identifier . . . . . . . . . . . . . . . . . . . . . . 21 9.1. GM/T OID . . . . . . . . . . . . . . . . . . . . . . . . 21 9.2. ISO OID . . . . . . . . . . . . . . . . . . . . . . . . . 21 Tse & Wong Expires March 16, 2018 [Page 2] InternetDraft September 2017 10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 12. Appendix A: Example Calculations . . . . . . . . . . . . . . 22 12.1. Example 1. . . . . . . . . . . . . . . . . . . . . . . . 22 12.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . 23 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 13.1. Normative References . . . . . . . . . . . . . . . . . . 24 13.2. Informative References . . . . . . . . . . . . . . . . . 24 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 1. Introduction SM4 [GBT.329072016] [ISO.IEC.180333.AMD2] is a cryptographic standard issued by the Organization of State Commercial Administration of China [OSCCA] as an authorized cryptographic algorithm for the use within China. The algorithm is published in public. SM4 is a symmetric encryption algorithm, specifically a blockcipher, designed for data encryption. 1.1. Purpose This document does not aim to introduce a new algorithm, but to provide a clear and open description of the SM4 algorithm in English, and also to serve as a stable reference for IETF documents that utilize this algorithm. While this document is similar to [SM4En] in nature, [SM4En] is a textual translation of the "SMS4" algorithm [SM4] published in 2006, while this document follows the updated description and structure of [GBT.329072016] published in 2016. Sections 1 to 7 of this document directly map to the corresponding sections numbers of the [GBT.329072016] standard for convenience of the reader. This document also provides additional information on the practical usage and implementation of SM4, specifying multiple modes of operations that are known to be used with SM4 and providing the SM4 OIDs. 1.2. History The "SMS4" algorithm (the former name of SM4) was invented by Shu Wang Lu [LSWBio], first published in 2003 as part of [GB.15629.112003], then published independently in 2006 [SM4] by OSCCA, officially renamed to "SM4" in 2012 in [GMT00022012] published by OSCCA, and finally standardized in 2016 as a Chinese Tse & Wong Expires March 16, 2018 [Page 3] InternetDraft September 2017 National Standard (GB Standard) [GBT.329072016]. SM4 is also standardized in [ISO.IEC.180333.AMD2] by the International Organization for Standardization in 2017. SMS4 was originally created for use in protecting wireless networks [SM4], and is mandated in the Chinese National Standard for Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure) [GB.15629.112003]. A proposal was made to adopt SMS4 into the IEEE 802.11i standard, but the algorithm was eventually not included due to concerns of introducing inoperability with existing ciphers. The latest SM4 standard [GBT.329072016] was proposed by OSCCA, standardized through TC 260 of the Standardization Administration of the People's Republic of China (SAC), and was drafted by the following individuals at the Data Assurance and Communication Security Research Center (DAS Center) of the Chinese Academy of Sciences, the China Commercial Cryptography Testing Center and the Beijing Academy of Information Science & Technology (BAIST): o ShuWang Lu o DaiWai Li o KaiYong Deng o Chao Zhang o Peng Luo o Zhong Zhang o Fang Dong o YingYing Mao o ZhenHua Liu 1.3. Applications SM4 (and SMS4) has prevalent hardware implementations [SM4FPGA] [SM4VLSI], due to its being the only OSCCAapproved symmetric encryption algorithm allowed for use in China. SM4 can be used with multiple modes (See Section 8). Tse & Wong Expires March 16, 2018 [Page 4] InternetDraft September 2017 1.4. Cryptanalysis A number of attacks have been attempted on SM4, such as [SM4Analysis] [SM4Linear], but there are no known feasible attacks against the SM4 algorithm by the time of publishing this document. There are, however, security concerns with regards to sidechannel attacks [SideChannel] when the SM4 algorithm is implemented in a hardware device [SM4Power]. For instance, [SM4Power] illustrated an attack by measuring the power consumption of the device. A chosen ciphertext attack, assuming a fixed correlation between the round keys and data mask, is able to recover the round key successfully. When the SM4 algorithm is implemented in hardware, the parameters and keys SHOULD be randomly generated without fixed correlation. There have been improvements to the hardware embodiment design for SM4, such as [SM4VLSI], that may resist such attacks. In order to improve security of the SM4 cryptographic process, secure whitebox implementations such as [SM4WhiteBox] have been proposed. Speed enhancements, such as [SM4HiSpeed], have also been proposed. 2. Terms and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. The following terms and definitions apply to this document. block length Bitlength of a message block. key length Bitlength of a key. key expansion algorithm An operation that converts a key into a round key. rounds The number of iterations that the round function is run. round key A key used in each round on the blockcipher, derived from the input key, also called a subkey. Tse & Wong Expires March 16, 2018 [Page 5] InternetDraft September 2017 word a 32bit quantity Sbox The S (substitution) box function produces 8bit output from 8bit input, represented as S(.) 3. Symbols And Abbreviations S xor T bitwise execlusiveor of two 32bit vectors S and T. S and T will always have the same length. a <<< i 32bit bitwise cyclic shift on a with i bits shifted left. 4. Compute Structure The SM4 algorithm is a blockcipher, with block size of 128 bits and a key length of 128 bits. Both encryption and key expansion uses 32 rounds of a nonlinear key schedule per block. Each round processes one of the four 32bit words that constitute the block. The structure of encryption and decryption are identical, except that the round key schedule has its order reversed during decryption. Using a 8bit Sbox, it only uses exclusiveor, cyclic bit shifts and Sbox lookups to execute. 5. Key And Key Parameters Encryption key length is 128bits, and represented below, where each MK_i, (i = 0, 1, 2, 3) is 32bits wide. MK = (MK_0, MK_1, MK_2, MK_3) The round key schedule is derived from the encryption key, represented as below where each rk_i (i = 0, ..., 31) is a word: (rk_0, rk_1, ... , rk_31) System parameters used for key expansion is represented as FK, where each FK_i (i = 0, ..., 3) is a word: FK = (FK_0, FK_1, FK_2, FK_3) Tse & Wong Expires March 16, 2018 [Page 6] InternetDraft September 2017 Constant parameters used for key expansion is represented as CK, where each CK_i (i = 0, ..., 31) is a word: CK = (CK_0, CK_1, ... , CK_31) 6. Functions 6.1. Round Function F The round function F is defined as: F(X_0, X_1, X_2, X_3, rk) = X_0 xor T(X_1 xor X_2 xor X_3 xor rk) Where: o Each $$X_i$ is 32 bits wide. o The round key rk is 32 bits wide. 6.2. Permutation T and T' T is a reversible permutation that outputs 32 bits from an input of 32 bits. It consists of a nonlinear transform tau and linear transform L. T(.) = L(tau(.)) The permutation T' is created from T by replacing the linear transform function L with L'. T'(.) = L'(tau(.)) 6.2.1. Nonlinear Transformation tau tau is composed of four parallel Sboxes. Given a 32bit input A, where each a_i is a 8bit string: A = (a_0, a_1, a_2, a_3) The output is a 32bit B, where each b_i is a 8bit string: B = (b_0, b_1, b_2, b_3) B is calculated as follows: (b_0, b_1, b_2, b_3) = tau(A) Tse & Wong Expires March 16, 2018 [Page 7] InternetDraft September 2017 tau(A) = (S(a_0), S(a_1), S(a_2), S(a_3)) 6.2.2. Linear Transformation L and L' The output of nonlinear transformation function tau is used as input to linear transformation function L. Given B, a 32bit input. The linear transformation L' is defined as follows. L(B) = B xor (B <<< 2) xor (B <<< 10) xor (B <<< 18) xor (B <<< 24) The linear transformation L' is defined as follows. L'(B) = B xor (B <<< 13) xor (B <<< 23) 6.2.3. Sbox S The Sbox S used in tau is given in this lookup table in hexadecimal form:  0 1 2 3 4 5 6 7 8 9 A B C D E F  0  D6 90 E9 FE CC E1 3D B7 16 B6 14 C2 28 FB 2C 05 1  2B 67 9A 76 2A BE 04 C3 AA 44 13 26 49 86 06 99 2  9C 42 50 F4 91 EF 98 7A 33 54 0B 43 ED CF AC 62 3  E4 B3 1C A9 C9 08 E8 95 80 DF 94 FA 75 8F 3F A6 4  47 07 A7 FC F3 73 17 BA 83 59 3C 19 E6 85 4F A8 5  68 6B 81 B2 71 64 DA 8B F8 EB 0F 4B 70 56 9D 35 6  1E 24 0E 5E 63 58 D1 A2 25 22 7C 3B 01 21 78 87 7  D4 00 46 57 9F D3 27 52 4C 36 02 E7 A0 C4 C8 9E 8  EA BF 8A D2 40 C7 38 B5 A3 F7 F2 CE F9 61 15 A1 9  E0 AE 5D A4 9B 34 1A 55 AD 93 32 30 F5 8C B1 E3 A  1D F6 E2 2E 82 66 CA 60 C0 29 23 AB 0D 53 4E 6F B  D5 DB 37 45 DE FD 8E 2F 03 FF 6A 72 6D 6C 5B 51 C  8D 1B AF 92 BB DD BC 7F 11 D9 5C 41 1F 10 5A D8 D  0A C1 31 88 A5 CD 7B BD 2D 74 D0 12 B8 E5 B4 B0 E  89 69 97 4A 0C 96 77 7E 65 B9 F1 09 C5 6E C6 84 F  18 F0 7D EC 3A DC 4D 20 79 EE 5F 3E D7 CB 39 48 For example, input "EF" will produce an output read from the Sbox table row E and column F, giving the result S(EF) = 84. Tse & Wong Expires March 16, 2018 [Page 8] InternetDraft September 2017 7. Calculations 7.1. Encryption The encryption algorithm consists of 32 rounds and 1 reverse transform R. Given a 128bit plaintext input, where each X_i is a 32bit word: (X_0, X_1, X_2, X_3) The output is a 128bit ciphertext, where each Y_i is a 32bit word: (Y_0, Y_1, Y_2, Y_3) Each round key is designated as rk_i, where each rk_i is a 32bit word and i = 0, 1, 2, ..., 31. a. 32 rounds of calculation i = 0, 1, ..., 31 X_{i+4} = F(X_i, X_{i+1}, X_{i+2}, X_{i+3}, rk_i) b. reverse transformation (Y_0, Y_1, Y_2, Y_3) = R(X_32, X_33, X_34, X_35) R(X_32, X_33, X_34, X_35) = (X_35, X_34, X_33, X_32) Please refer to Section 12 for sample calculations. 7.2. Decryption Decryption takes an identical process as encryption, with the only difference the order of the round key sequence. During decryption, the round key sequence is: (rk_31, rk_30, ..., rk_0) 7.3. Key Schedule Round keys used during encryption are derived from the encryption key. Specifically, given the encryption key MK, where each MK_i is 32 bits wide: Tse & Wong Expires March 16, 2018 [Page 9] InternetDraft September 2017 MK = (MK_0, MK_1, MK_2, MK_3) Each round key rk_i is created as follows, where i = 0, 1, ..., 31. (K_0, K_1, K_2, K_3) = (MK_0 xor FK_0, MK_1 xor FK_1, MK_2 xor FK_2, MK_3 xor FK_3) rk_i = K_{i + 4} K_{i + 4} = K_i xor T' (K_{i + 1} xor K_{i + 2} xor K_{i + 3} xor CK_i) Since the decryption key is identical to the encryption key, the round keys used in the decryption process are derived from the decryption key through the identical process to that of during encryption. 7.3.1. System Parameter FK System parameter FK given in hexadecimal notation, is: FK_0 = A3B1BAC6 FK_1 = 56AA3350 FK_2 = 677D9197 FK_3 = B27022DC 7.3.2. Constant Parameter CK The method to retrieve values from the constant parameter CK is as follows. Let ck_{i, j} be the jth byte (i = 0, 1, ..., 31; j = 0, 1, 2, 3) of CK_i. Therefore, each ck_{i, j} is a 8bit string, and each CK_i a 32bit word. CK_i = (ck_{i, 0}, ck_{i, 1}, ck_{i, 2}, ck_{i, 3}) ck_{i, j} = (4i + j) x 7 (mod 256) The constant parameter CK_i, (i = 0, 1, ..., 31) values, in hexadecimal, are: Tse & Wong Expires March 16, 2018 [Page 10] InternetDraft September 2017 CK_0 = 00070E15 CK_16 = C0C7CED5 CK_1 = 1C232A31 CK_17 = DCE3EAF1 CK_2 = 383F464D CK_18 = F8FF060D CK_3 = 545B6269 CK_19 = 141B2229 CK_4 = 70777E85 CK_20 = 30373E45 CK_5 = 8C939AA1 CK_21 = 4C535A61 CK_6 = A8AFB6BD CK_22 = 686F767D CK_7 = C4CBD2D9 CK_23 = 848B9299 CK_8 = E0E7EEF5 CK_24 = A0A7AEB5 CK_9 = FC030A11 CK_25 = BCC3CAD1 CK_10 = 181F262D CK_26 = D8DFE6ED CK_11 = 343B4249 CK_27 = F4FB0209 CK_12 = 50575E65 CK_28 = 10171E25 CK_13 = 6C737A81 CK_29 = 2C333A41 CK_14 = 888F969D CK_30 = 484F565D CK_15 = A4ABB2B9 CK_31 = 646B7279 8. Modes of Operation This document defines multiple modes of operation for the SM4 blockcipher algorithm. The CBC (Cipher Block Chaining), ECB (Electronic CodeBook), CFB (Cipher FeedBack), OFB (Output FeedBack) and CTR (Counter) modes are defined in [NIST.SP.80038A] and utilized with the SM4 algorithm in the following sections. 8.1. Variables And Primitives Hereinafter we define: SM4Encrypt(P, K) The SM4 algorithm that encrypts plaintext P with key K, described in Section 7.1 SM4Decrypt(C, K) The SM4 algorithm that decrypts ciphertext C with key K, described in Section 7.2 b block size in bits, defined as 128 for SM4 P_j block j of ciphertext bitstring P C_j block j of ciphertext bitstring C Tse & Wong Expires March 16, 2018 [Page 11] InternetDraft September 2017 NBlocks(B, b) Number of blocks of size bbits in bitstring B IV Initialization vector LSB(b, S) Least significant b bits of the bitstring S MSB(b, S) Most significant b bits of the bitstring S 8.2. Initialization Vectors The CBC, CFB and OFB modes require an additional input to the encryption process, called the initialization vector (IV). The identical IV is used in the input of encryption as well as the decryption of the corresponding ciphertext. Generation of IV values MUST take into account of the considerations in Section 10 recommended by [BCEVAL]. 8.3. SM4ECB In SM4ECB, the same key is utilized to create a fixed assignment for a plaintext block with a ciphertext block, meaning that a given plaintext block always gets encrypted to the same ciphertext block. As described in [NIST.SP.80038A], this mode should be avoided if this property is undesirable. This mode requires input plaintext to be a multiple of the block size, which in this case of SM4 it is 128bits. It also allows multiple blocks to be computed in parallel. 8.3.1. SM4ECB Encryption Inputs: o P, plaintext, length MUST be multiple of b o K, SM4 128bit encryption key Output: o C, ciphertext, length is a multiple of b C is defined as follows. Tse & Wong Expires March 16, 2018 [Page 12] InternetDraft September 2017 n = NBlocks(P, b) for i = 1 to n C_i = SM4Encrypt(P_i, K) end for C = C_1  ...  C_n 8.3.2. SM4ECB Decryption Inputs: o C, ciphertext, length MUST be multiple of b o K, SM4 128bit encryption key Output: o P, plaintext, length is a multiple of b P is defined as follows. n = NBlocks(C, b) for i = 1 to n P_i = SM4Decrypt(C_i, K) end for P = P_1  ...  P_n 8.4. SM4CBC SM4CBC is similar to SM4ECB that the input plaintext MUST be a multiple of the block size, which is 128bits in SM4. SM4CBC requires an additional input, the IV, that is unpredictable for a particular execution of the encryption process. Since CBC encryption relies on a forward cipher operation that depend on results of the previous operation, it cannot be parallelized. However, for decryption, since ciphertext blocks are already available, CBC parallel decryption is possible. 8.4.1. SM4CBC Encryption Inputs: o P, plaintext, length MUST be multiple of b Tse & Wong Expires March 16, 2018 [Page 13] InternetDraft September 2017 o K, SM4 128bit encryption key o IV, 128bit, unpredictable, initialization vector Output: o C, ciphertext, length is a multiple of b C is defined as follows. n = NBlocks(P, b) C_1 = SM4Encrypt(P_1 xor IV, K) for i = 2 to n C_i = SM4Encrypt(P_i xor C_{i  1}, K) end for C = C_1  ...  C_n 8.4.2. SM4CBC Decryption Inputs: o C, ciphertext, length MUST be a multiple of b o K, SM4 128bit encryption key o IV, 128bit, unpredictable, initialization vector Output: o P, plaintext, length is multiple of b P is defined as follows. n = NBlocks(C, b) P_1 = SM4Decrypt(C_1, K) xor IV for i = 2 to n P_i = SM4Decrypt(C_i, K) xor C_{i  1} end for P = P_1  ...  P_n Tse & Wong Expires March 16, 2018 [Page 14] InternetDraft September 2017 8.5. SM4CFB SM4CFB relies on feedback provided by successive ciphertext segments to generate output blocks. The plaintext given must be a multiple of the block size. Similar to SM4CBC, SM4CFB requires an IV that is unpredictable for a particular execution of the encryption process. SM4CFB further allows setting a positive integer parameter s, that is less than or equal to the block size, to specify the size of each data segment. The same segment size must be used in encryption and decryption. In SM4CFB, since the input block to each forward cipher function depends on the output of the previous block (except the first that depends on the IV), encryption is not parallizable. Decryption, however, can be parallelized. 8.5.1. SM4CFB Variants SM4CFB takes an integer s to determine segment size in its encryption and decryption routines. We define the following variants of SM4CFB for various s: o SM4CFB1, the 1bit SM4CFB mode, where s is set to 1. o SM4CFB8, the 8bit SM4CFB mode, where s is set to 8. o SM4CFB64, the 64bit SM4CFB mode, where s is set to 64. o SM4CFB128, the 128bit SM4CFB mode, where s is set to 128. 8.5.2. SM4CFB Encryption Inputs: o P#, plaintext, length MUST be multiple of s o K, SM4 128bit encryption key o IV, 128bit, unpredictable, initialization vector o s, an integer 1 <= s <= b that defines segment size Output: o C#, ciphertext, length is a multiple of s Tse & Wong Expires March 16, 2018 [Page 15] InternetDraft September 2017 C# is defined as follows. n = NBlocks(P#, s) I_1 = IV for i = 2 to n I_i = LSB(b  s, I_{i  1})  C#_{j  1} end for for i = 1 to n O_j = SM4Encrypt(I_i, K) end for for i = 1 to n C#_i = P#_1 xor MSB(s, O_j) end for C# = C#_1  ...  C#_n 8.5.3. SM4CFB Decryption Inputs: o C#, ciphertext, length MUST be a multiple of s o K, SM4 128bit encryption key o IV, 128bit, unpredictable, initialization vector o s, an integer 1 <= s <= b that defines segment size Output: o P#, plaintext, length is multiple of s P is defined as follows. Tse & Wong Expires March 16, 2018 [Page 16] InternetDraft September 2017 n = NBlocks(P#, s) I_1 = IV for i = 2 to n I_i = LSB(b  s, I_{i  1})  C#_{j  1} end for for i = 1 to n O_j = SM4Encrypt(I_i, K) end for for i = 1 to n P#_i = C#_1 xor MSB(s, O_j) end for P# = P#_1  ...  P#_n 8.6. SM4OFB SM4OFB is the application of SM4 through the Output Feedback mode. This mode requires that the IV is a nonce, meaning that the IV MUST be unique for each execution for an input key. OFB does not require the input plaintext to be a multiple of the block size. In OFB, the routines for encryption and decryption are identical. As each forward cipher function (except the first) depends on previous results, both routines cannot be parallelized. However given a known IV, output blocks could be generated prior to the input of plaintext (encryption) or ciphertext (decryption). 8.6.1. SM4OFB Encryption Inputs: o P, plaintext, composed of (n  1) blocks of size b, with the last block P_n of size 1 <= u <= b o K, SM4 128bit encryption key o IV, a nonce (a unique value for each execution per given key) Output: o C, ciphertext, composed of (n  1) blocks of size b, with the last block C_n of size 1 <= u <= b C is defined as follows. Tse & Wong Expires March 16, 2018 [Page 17] InternetDraft September 2017 n = NBlocks(P, b) I_1 = IV for i = 1 to (n  1) O_i = SM4Encrypt(I_i) I_{i + 1} = O_i end for for i = 1 to (n  1) C_i = P_i xor O_i end for C_n = P_n xor MSB(u, O_n) C = C_1  ...  C_n 8.6.2. SM4OFB Decryption Inputs: o C, ciphertext, composed of (n  1) blocks of size b, with the last block C_n of size 1 <= u <= b o K, SM4 128bit encryption key o IV, the nonce used during encryption Output: o P, plaintext, composed of (n  1) blocks of size b, with the last block P_n of size 1 <= u <= b C is defined as follows. Tse & Wong Expires March 16, 2018 [Page 18] InternetDraft September 2017 n = NBlocks(C, b) I_1 = IV for i = 1 to (n  1) O_i = SM4Encrypt(I_i) I_{i + 1} = O_i end for for i = 1 to (n  1) P_i = C_i xor O_i end for P_n = C_n xor MSB(u, O_n) P = P_1  ...  P_n 8.7. SM4CTR SM4CTR is an implementation of a stream cipher through a block cipher primitive. It generates a "keystream" of keys that are used to encrypt successive blocks, with the keystream created from the input key, a nonce (the IV) and an incremental counter. The counter could be any sequence that does not repeat within the block size. Both SM4CTR encryption and decryption routines could be parallelized, and random access is also possible. 8.7.1. SM4CTR Encryption Inputs: o P, plaintext, composed of (n  1) blocks of size b, with the last block P_n of size 1 <= u <= b o K, SM4 128bit encryption key o IV, a nonce (a unique value for each execution per given key) o T, a sequence of counters from T_1 to T_n Output: o C, ciphertext, composed of (n  1) blocks of size b, with the last block C_n of size 1 <= u <= b C is defined as follows. Tse & Wong Expires March 16, 2018 [Page 19] InternetDraft September 2017 n = NBlocks(P, b) for i = 1 to n O_i = SM4Encrypt(T_i) end for for i = 1 to (n  1) C_i = P_i xor O_i end for C_n = P_n xor MSB(u, O_n) C = C_1  ...  C_n 8.7.2. SM4CTR Encryption Inputs: o C, ciphertext, composed of (n  1) blocks of size b, with the last block C_n of size 1 <= u <= b o K, SM4 128bit encryption key o IV, a nonce (a unique value for each execution per given key) o T, a sequence of counters from T_1 to T_n Output: o P, plaintext, composed of (n  1) blocks of size b, with the last block P_n of size 1 <= u <= b P is defined as follows. n = NBlocks(C, b) for i = 1 to n O_i = SM4Encrypt(T_i) end for for i = 1 to (n  1) P_i = C_i xor O_i end for P_n = C_n xor MSB(u, O_n) C = C_1  ...  C_n Tse & Wong Expires March 16, 2018 [Page 20] InternetDraft September 2017 9. Object Identifier The Object Identifier for SM4 is identified through these OIDs. 9.1. GM/T OID "1.2.156.10197.1.104" for "SM4 Algorithm" [GMT00062012]. 9.2. ISO OID "1.0.18033.3.2.4" for "idbc128sm4" [ISO.IEC.180333.AMD2], described below. is180333 OID ::= {iso(1) standard(0) is18033(18033) part3(3)} idbc128 OID ::= {is180333 blockcipher128bit(2)} idbc128sm4 OID ::= {idbc128 sm4(4)} 10. Security Considerations o Products and services that utilize cryptography are regulated by OSCCA [OSCCA]; they must be explicitly approved or certified by OSCCA before being allowed to be sold or used in China. o SM4 is a blockcipher symmetric algorithm with key length of 128 bits. It is considered as an alternative to AES128 [NIST.FIPS.197]. o SM4 [GBT.329072016] is a blockcipher certified by OSCCA [OSCCA]. No formal proof of security is provided. There are no known feasible attacks against SM4 algorithm by the time of publishing this document, but there are security concerns with regards to sidechannel attacks when the SM4 algorithm is implemented in hardware. See Section 1.4 for more details. o The IV does not have to be secret. The IV itself, or criteria enough to determine it, MAY be transmitted with ciphertext. o SM4ECB: ECB is one of the four original modes defined for DES. With its problem well known to "leak quite a large amount of information" [BCEVAL], it SHOULD NOT be used in most cases. o SM4CBC, SM4CFB, SM4OFB: CBC, CFB and OFB are IVbased modes of operation that were originally defined for DES. When using these modes of operation, the IV SHOULD be random to preserve message confidentiality [BCEVAL]. It is shown in the same document that CBC, CFB, OFB, the variants #CBC, #CFB that utilize the Tse & Wong Expires March 16, 2018 [Page 21] InternetDraft September 2017 recommendation of [NIST.SP.80038A] to make CBC and CFB noncebased, are SemCPA secure as probabilistic encryption schemes. Various attack scenarios have been described in [BCEVAL] and these modes SHOULD NOT be used unless for compatibility reasons. o SM4CTR: CTR is considered to be the "best" mode of operation within [NIST.SP.80038A] as it is considered SemCPA secure as a noncebased encryption scheme, providing provablesecurity guarantees as good as the classic modes of operation (ECB, CBC, CFB, OFB) [BCEVAL]. Users with no need of authenticity, nonmalleablility and chosen ciphertext (CCA) security MAY utilize this mode of operation [BCEVAL]. 11. IANA Considerations This document does not require any action by IANA. 12. Appendix A: Example Calculations 12.1. Example 1. This example demonstrates encryption of a plaintext. Plaintext: 01 23 45 67 89 AB CD EF FE DC BA 98 76 54 32 10 Encryption key: 01 23 45 67 89 AB CD EF FE DC BA 98 76 54 32 10 Status of the round key (rk_i) and round output (X_i) per round: Tse & Wong Expires March 16, 2018 [Page 22] InternetDraft September 2017 rk_0 = F12186F9 X_4 = 27FAD345 rk_1 = 41662B61 X_5 = A18B4CB2 rk_2 = 5A6AB19A X_6 = 11C1E22A rk_3 = 7BA92077 X_7 = CC13E2EE rk_4 = 367360F4 X_8 = F87C5BD5 rk_5 = 776A0C61 X_9 = 33220757 rk_6 = B6BB89B3 X_10 = 77F4C297 rk_7 = 24763151 X_11 = 7A96F2EB rk_8 = A520307C X_12 = 27DAC07F rk_9 = B7584DBD X_13 = 42DD0F19 rk_10 = C30753ED X_14 = B8A5DA02 rk_11 = 7EE55B57 X_15 = 907127FA rk_12 = 6988608C X_16 = 8B952B83 rk_13 = 30D895B7 X_17 = D42B7C59 rk_14 = 44BA14AF X_18 = 2FFC5831 rk_15 = 104495A1 X_19 = F69E6888 rk_16 = D120B428 X_20 = AF2432C4 rk_17 = 73B55FA3 X_21 = ED1EC85E rk_18 = CC874966 X_22 = 55A3BA22 rk_19 = 92244439 X_23 = 124B18AA rk_20 = E89E641F X_24 = 6AE7725F rk_21 = 98CA015A X_25 = F4CBA1F9 rk_22 = C7159060 X_26 = 1DCDFA10 rk_23 = 99E1FD2E X_27 = 2FF60603 rk_24 = B79BD80C X_28 = EFF24FDC rk_25 = 1D2115B0 X_29 = 6FE46B75 rk_26 = 0E228AEB X_30 = 893450AD rk_27 = F1780C81 X_31 = 7B938F4C rk_28 = 428D3654 X_32 = 536E4246 rk_29 = 62293496 X_33 = 86B3E94F rk_30 = 01CF72E5 X_34 = D206965E rk_31 = 9124A012 X_35 = 681EDF34 Ciphertext: 68 1E DF 34 D2 06 96 5E 86 B3 E9 4F 53 6E 42 46 12.2. Example 2 This example demonstrates encryption of a plaintext 1,000,000 times repeatedly using a fixed encryption key. Plaintext: 01 23 45 67 89 AB CD EF FE DC BA 98 76 54 32 10 Encryption Key: 01 23 45 67 89 AB CD EF FE DC BA 98 76 54 32 10 Ciphertext: 59 52 98 C7 C6 FD 27 1F 04 02 F8 04 C3 3D 3F 66 Tse & Wong Expires March 16, 2018 [Page 23] InternetDraft September 2017 13. References 13.1. Normative References [GBT.329072016] Standardization Administration of the People's Republic of China, "GB/T 329072016: Information security technology  SM4 block cipher algorithm", August 2016, <http://www.gb688.cn/bzgk/gb/ newGbInfo?hcno=7803DE42D3BC5E80B0C3E5D8E873D56A>. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfceditor.org/info/rfc2119>. 13.2. Informative References [BCEVAL] University of California, Davis, "Evaluation of Some Blockcipher Modes of Operation", February 2011, <http://web.cs.ucdavis.edu/~rogaway/papers/modes.pdf>. [GB.15629.112003] Standardization Administration of the People's Republic of China, "Information technology  Telecommunications and information exchange between systems  Local and metropolitan area networks  Specific requirements  Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", May 2003, <http://www.gb688.cn/bzgk/gb/ newGbInfo?hcno=74B9DD11287E72408C19C4D3A360D1BD>. [GMT00022012] Organization of State Commercial Administration of China, "GM/T 00022012: SM4 block cipher algorithm", March 2012, <http://www.oscca.gov.cn/Column/Column_32.htm>. [GMT00062012] Organization of State Commercial Administration of China, "GM/T 00062012: Cryptographic Application Identifier Criterion Specification", March 2012, <http://www.oscca.gov.cn/Column/Column_32.htm>. [ISO.IEC.180333.AMD2] International Organization for Standardization, "ISO/IEC WD1 180333/AMD2  Encryption algorithms  Part 3: Block ciphers  Amendment 2", June 2017, <https://www.iso.org/standard/54531.html>. Tse & Wong Expires March 16, 2018 [Page 24] InternetDraft September 2017 [LSWBio] Sun, M., "Lv Shu Wang  A life in cryptography", November 2010, <http://press.ustc.edu.cn/sites/default/files/fujian/field _fujian_multi/20120113/%E5%90%95%E8%BF%B0%E6%9C%9B%20%E5%A F%86%E7%A0%81%E4%B8%80%E6%A0%B7%E7%9A%84%E4%BA%BA%E7%94%9F .pdf>. [NIST.FIPS.197] National Institute of Standards and Technology, "NIST FIPS 197: Advanced Encryption Standard (AES)", November 2001, <https://doi.org/10.6028/NIST.FIPS.197>. [NIST.SP.80038A] Dworkin, M., "NIST Special Publication 80038A: Recommendation for Block Cipher Modes of Operation  Methods and Techniques", December 2001, <http://dx.doi.org/10.6028/NIST.SP.80038A>. [OSCCA] Organization of State Commercial Administration of China, "Organization of State Commercial Administration of China", May 2017, <http://www.oscca.gov.cn>. [SideChannel] Lei, Q., Wu, L., Zhang, S., Zhang, X., Li, X., Pan, L., and Z. Dong, "Software Hardware Codesign for SideChannel Analysis Platform on Security Chips", December 2015, <https://doi.org/10.1109/CIS.2015.102>. [SM4] Organization of State Commercial Administration of China, "SMS4 Cryptographic Algorithm For Wireless LAN Products", January 2006, <http://www.oscca.gov.cn/UpFile/200621016423197990.pdf>. [SM4Analysis] Kim, T., Kim, J., Kim, S., and J. Sung, "Linear and Differential Cryptanalysis of Reduced SMS4 Block Cipher", June 2008, <https://eprint.iacr.org/2008/281>. [SM4En] Diffie, W. and G. Ledin, "SMS4 Encryption Algorithm for Wireless Networks", May 2008, <https://www.iacr.org/cryptodb/data/ paper.php?pubkey=18006>. Tse & Wong Expires March 16, 2018 [Page 25] InternetDraft September 2017 [SM4FPGA] Cheng, H., Zhai, S., Fang, L., Ding, Q., and C. Huang, "Improvements of SM4 Algorithm and Application in Ethernet Encryption System Based on FPGA", July 2014, <https://www.researchgate.net/publication/287081686_Improv ements_of_SM4_algorithm_and_application_in_Ethernet_encryp tion_system_based_on_FPGA>. [SM4HiSpeed] Lv, Q., Li, L., and Y. Cao, "Highspeed Encryption & Decryption System Based on SM4", July 2016, <http://dx.doi.org/10.14257/ijsia.2016.10.9.01>. [SM4Linear] Liu, M. and J. Chen, "Improved Linear Attacks on the Chinese Block Cipher Standard", November 2014, <https://doi.org/10.1007/s1139001414959>. [SM4Power] Du, Z., Wu, Z., Wang, M., and J. Rao, "Improved chosen plaintext power analysis attack against SM4 at the round output", October 2015, <http://dx.doi.org/10.6028/NIST.FIPS.1804>. [SM4VLSI] Yu, S., Li, K., Li, K., Qin, Y., and Z. Tong, "A VLSI implementation of an SM4 algorithm resistant to power analysis", July 2016, <https://doi.org/10.3233/JIFS169011>. [SM4WhiteBox] Bai, K. and C. Wu, "A secure whitebox SM4 implementation", May 2008, <http://dx.doi.org/10.1002/sec.1394>. Appendix A. Acknowledgements The authors would like to thank the following persons for their valuable advice and input. o Jack Lloyd and Daniel Wyatt of the Ribose rnp team for their input and implementation Authors' Addresses Tse & Wong Expires March 16, 2018 [Page 26] InternetDraft September 2017 Ronald Henry Tse Ribose Suite 1111, 1 Pedder Street Central, Hong Kong Hong Kong Email: ronald.tse@ribose.com URI: https://www.ribose.com Dr. Wai Kit Wong Hang Seng Management College Hang Shin Link, Siu Lek Yuen Shatin, New Territories Hong Kong Email: wongwk@hsmc.edu.hk URI: https://www.hsmc.edu.hk Tse & Wong Expires March 16, 2018 [Page 27]