How to Integrate a Symmetric Cipher - Revision history

Levitte: /* Changes to Configure */

2021-04-18T07:22:10Z

Changes to Configure

Rschmicker: Rschmicker moved page How to Integrate Symmetric Cipher to How to Integrate a Symmetric Cipher: missing "a"

2017-05-23T14:56:47Z

Rschmicker moved page How to Integrate Symmetric Cipher to How to Integrate a Symmetric Cipher: missing "a"

Rschmicker: /* Error/Reason Codes */

2017-05-23T04:10:48Z

Error/Reason Codes

Rschmicker at 04:07, 23 May 2017

2017-05-23T04:07:37Z

Rschmicker: /* Speed Test */

2017-05-08T23:15:43Z

Speed Test

Rschmicker: /* Cipher Initialization Function */

2017-05-08T23:14:04Z

Cipher Initialization Function

Rschmicker: /* Key Initialization Function */

2017-05-08T23:13:35Z

Key Initialization Function

Rschmicker: /* Speed Test */

2017-05-08T23:10:28Z

Speed Test

Rschmicker at 23:08, 8 May 2017

2017-05-08T23:08:45Z

Rschmicker: /* Speed Test */

2017-05-08T23:07:05Z

Speed Test

@@ Line 64: / Line 64: @@
      ];
-The following steps are optional if you would like to have the cipher be disabled, should someone compiling choose to do so. Start by including ARIA to the disables table.
+The following steps are optional if you would like to have the cipher be enabled or disabled, should someone compiling choose to do so. Start by including ARIA to the disablables table.
   my @disablables = (

@@ Line 265: / Line 265: @@
 === Error/Reason Codes ===
-Error codes are handled dynamically in OpenSSL by using make update. make update will, in part, call make errors which will later execute util/mkerr.pl recursively on crypto/*.c, crypto/*/*.c, ssl/*.c, and apps/*.c.  This script will scan for error and function codes and automatically add them as error/reason codes in the library. Essentially, it will look for strings that "look like" function or reason codes: basically anything consisting of all upper case and numerics which has _F_ or _R_ in it and which has the name of an error library at the start. For example,
+Error codes are handled dynamically in OpenSSL by using make update. make update will, in part, call make errors which will later execute util/mkerr.pl recursively on crypto/*.c, crypto/*/*.c, ssl/*.c, and apps/*.c.  This script will scan for error and function codes and automatically add them as error/reason codes in the library. Essentially, it will look for strings that "look like" function or reason codes: basically anything consisting of all upper case and numerics which has _F_ or _R_ in it and which has the name of an error library at the start. For example, EVP_F_ARIA_INIT_KEY and EVP_R_ARIA_KEY_SETUP_FAILED. For more detailed documentation please view crypto/err/README and util/mkerr.pl.
 == Crypto Objects ==

@@ Line 261: / Line 261: @@
   #endif
-This adds all of the cipher chaining modes that were provided by the e_aria.c files except for CTR mode. It also includes some aliases for the CBC modes. ARIA also has some optional but recommended custom error messages. These are added to the crypto/evp/evp_err.c file:
+This adds all of the cipher chaining modes that were provided by the e_aria.c files except for CTR mode. It also includes some aliases for the CBC modes.
- static ERR_STRING_DATA EVP_str_functs[] = {
+=== Error/Reason Codes ===
-and
+Error codes are handled dynamically in OpenSSL by using make update. make update will, in part, call make errors which will later execute util/mkerr.pl recursively on crypto/*.c, crypto/*/*.c, ssl/*.c, and apps/*.c.  This script will scan for error and function codes and automatically add them as error/reason codes in the library. Essentially, it will look for strings that "look like" function or reason codes: basically anything consisting of all upper case and numerics which has _F_ or _R_ in it and which has the name of an error library at the start. For example,
-  static ERR_STRING_DATA EVP_str_reasons[] = {
+  {ERR_FUNC(EVP_F_ARIA_INIT_KEY), "aria_init_key"},
-  ...
-     {ERR_REASON(EVP_R_ARIA_KEY_SETUP_FAILED), "aria key setup failed"},
+will list the function name and
 == Crypto Objects ==

@@ Line 651: / Line 651: @@
              for (count = 0, run = 1; COND(c[D_CBC_128_ARIA][testnum]); count++)
                  ARIA_cbc_encrypt(loopargs[0].buf, loopargs[0].buf,
-                                     (size_t)lengths[testnum], &aria_ks1,
+                                 (size_t)lengths[testnum], &aria_ks1,
-                                     iv, ARIA_ENCRYPT);
+                                 iv, ARIA_ENCRYPT);
              d = Time_F(STOP);
              print_result(D_CBC_128_ARIA, testnum, count, d);
@@ Line 673: / Line 673: @@
              for (count = 0, run = 1; COND(c[D_CBC_192_ARIA][testnum]); count++)
                  ARIA_cbc_encrypt(loopargs[0].buf, loopargs[0].buf,
-                                     (size_t)lengths[testnum], &aria_ks2,
+                                 (size_t)lengths[testnum], &aria_ks2,
-                                     iv, ARIA_ENCRYPT);
+                                 iv, ARIA_ENCRYPT);
              d = Time_F(STOP);
              print_result(D_CBC_192_ARIA, testnum, count, d);
@@ Line 691: / Line 691: @@
              for (count = 0, run = 1; COND(c[D_CBC_256_ARIA][testnum]); count++)
                  ARIA_cbc_encrypt(loopargs[0].buf, loopargs[0].buf,
-                                     (size_t)lengths[testnum], &aria_ks3,
+                                 (size_t)lengths[testnum], &aria_ks3,
-                         iv, ARIA_ENCRYPT);
+                                 iv, ARIA_ENCRYPT);
              d = Time_F(STOP);
              print_result(D_CBC_256_ARIA, testnum, count, d);

@@ Line 202: / Line 202: @@
       union {
           void (*cipher) (MYKEY *k, size_t len, const unsigned char *in,
-                                    unsigned char *out);
+                         unsigned char *out);
       } stream;
   } EVP_MYCIPHER_KEY;

← Older revision	Revision as of 14:56, 23 May 2017
(No difference)

@@ Line 167: / Line 167: @@
      if (mode==EVP_CIPH_CFB_MODE||mode==EVP_CIPH_OFB_MODE||enc)
          ret = ARIA_set_encrypt_key(key, EVP_CIPHER_CTX_key_length(ctx) * 8,
-                                        EVP_CIPHER_CTX_get_cipher_data(ctx));
+                                   EVP_CIPHER_CTX_get_cipher_data(ctx));
      else
          ret = ARIA_set_decrypt_key(key, EVP_CIPHER_CTX_key_length(ctx) * 8,
-                                        EVP_CIPHER_CTX_get_cipher_data(ctx));
+                                   EVP_CIPHER_CTX_get_cipher_data(ctx));
      if(ret < 0) {
          EVPerr(EVP_F_ARIA_INIT_KEY,EVP_R_ARIA_KEY_SETUP_FAILED);

@@ Line 559: / Line 559: @@
 === Speed Test ===
-Just as it was explained the the TLS section, the speed test integration is optional and only needs to be implemented if desired. That being said, it is possible to natively integrate ARIA into OpenSSL's built in speed test, however, once a cipher is integrated into the EVP the speed test can access the cipher using the -evp flag. For completeness sake, the following steps are necessary to manually integrated ARIA into OpenSSL's speedtest.
+Just as it was explained in the TLS section, the speed test integration is optional and only needs to be implemented if desired. That being said, it is possible to natively integrate ARIA into OpenSSL's built in speed test, however, once a cipher is integrated into the EVP the speed test can access the cipher using the -evp flag. For completeness sake, the following steps are necessary to manually integrated ARIA into OpenSSL's speedtest.
 First the ARIA header file needs to be conditionally included:

@@ Line 336: / Line 336: @@
   # define EVP_R_ARIA_KEY_SETUP_FAILED      163
 == TLS ==
@@ Line 517: / Line 523: @@
 These values are pulled from ARIA'a RFC and others can be added if desired. Once the integration is complete with the remaining steps below, the test suite can be ran with make test.
 == Applications ==