Cryptogams AES - Revision history

Jwalton: Add info on Apple M1 builds.

2021-03-14T06:09:53Z

Add info on Apple M1 builds.

Jwalton: Use linux64, not linux32, for ARMv8 builds.

2021-03-12T15:00:18Z

Use linux64, not linux32, for ARMv8 builds.

Jwalton: Update title for ARMv8 AES builds.

2021-03-12T14:53:11Z

Update title for ARMv8 AES builds.

Jwalton: Add info on ARMv8 programs.

2021-03-12T14:48:31Z

Add info on ARMv8 programs.

Jwalton: Remove alignment from discussion. Alignment is handled by the module.

2019-05-25T14:33:21Z

Remove alignment from discussion. Alignment is handled by the module.

Jwalton: Add additional information.

2019-05-24T01:34:43Z

Add additional information.

Jwalton: Add additional information.

2019-05-24T01:27:37Z

Add additional information.

Jwalton: Add info on symbol names

2019-05-23T12:38:30Z

Add info on symbol names

Jwalton: Add arm_arch.h copy.

2019-05-23T09:00:17Z

Add arm_arch.h copy.

Jwalton: Add info on compiling with Clang and -mthumb.

2019-05-21T07:44:47Z

Add info on compiling with Clang and -mthumb.

@@ Line 470: / Line 470: @@
 * <tt>aes_v8_encrypt</tt>
 * <tt>aes_v8_decrypt</tt>
 [[Category:Cryptogams]]

@@ Line 459: / Line 459: @@
 If you need AES for ARMv8 devices, which includes aarch64 and aarch32, then use <tt>aesv8-armx.pl</tt>. You would use something like this in your scripts:
-<pre>if ! perl aesv8-armx.pl linux32 armx_aes.S; then
+<pre>if ! perl aesv8-armx.pl linux64 armx_aes.S; then
      echo "Failed to translate AES source file"
      exit 1

@@ Line 455: / Line 455: @@
 endif</pre>
-== ARMv8 ==
+== ARMv8 Builds ==
 If you need AES for ARMv8 devices, which includes aarch64 and aarch32, then use <tt>aesv8-armx.pl</tt>. You would use something like this in your scripts:

← Older revision		Revision as of 14:48, 12 March 2021
Line 454:		Line 454:

	endif</pre>		endif</pre>
		+
		+	== ARMv8 ==
		+
		+	If you need AES for ARMv8 devices, which includes aarch64 and aarch32, then use <tt>aesv8-armx.pl</tt>. You would use something like this in your scripts:
		+
		+	<pre>if ! perl aesv8-armx.pl linux32 armx_aes.S; then
		+	echo "Failed to translate AES source file"
		+	exit 1
		+	fi</pre>
		+
		+	<tt>aesv8-armx.pl</tt> provides the following functions:
		+
		+	* <tt>aes_v8_set_encrypt_key</tt>
		+	* <tt>aes_v8_set_decrypt_key</tt>
		+	* <tt>aes_v8_encrypt</tt>
		+	* <tt>aes_v8_decrypt</tt>

	[[Category:Cryptogams]]		[[Category:Cryptogams]]

@@ Line 5: / Line 5: @@
 There are 6 steps to the process. The first step obtains the sources. The second step creates an ASM source file. The third step compiles and assembles the source file into an object file. The fourth steps determines the API. The fifth step creates a C header file. The final step integrates the object file into a program. Once you create the files <tt>aes-armv4.h</tt> and <tt>aes-armv4.S</tt> you can use <tt>sed</tt> to restore symbols back to their Cryptogams name with <tt>sed -i 's|OPENSSL|CRYPTOGAMS|g' aes-armv4.h aes-armv4.S</tt>.
-A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation operates in ECB mode and encrypts or decrypts full AES blocks. You are responsible for things like data alignment, padding and side channel counter-measures.
+A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation operates in ECB mode and encrypts or decrypts full AES blocks. You are responsible for things like padding and side channel counter-measures.
 At the moment Clang is miscompiling <tt>aes-armv4.S</tt>. Also see [https://bugs.llvm.org/show_bug.cgi?id=38133 LLVM Issue 38133]. You can work around the problem by compiling <tt>aes-armv4.S</tt> with <tt>-mthumb</tt>, but all data must be aligned. If you don't use aligned buffers then a <tt>SIGBUS</tt> could occur.

@@ Line 301: / Line 301: @@
 The article used the same names as they appeared in the Cryptogams source code. For example, <tt>AES_set_encrypt_key</tt> and <tt>AES_set_decrypt_key</tt> are the names of two functions in the source code, and they will show up in the object file and when compiled and the library when linked.
-It is possible the function and date names will collide if you also link to OpenSSL, either directly or indirectly. If you plan on using Cryptogams code in a shared object then you should rename all symbols to avoid collisions. To rename symbols for SHA-1 you should rename <tt>sha1_block_data_order</tt> and <tt>OPENSSL_armcap_P</tt>. Assuming you are using <tt>MYLIB</tt> as a prefix the following <tt>sed</tt> should do the job.
+It is possible the function and date names will collide if you also link to OpenSSL, either directly or indirectly. If you plan on using Cryptogams code in a shared object then you should rename all symbols to avoid collisions. To rename symbols for AES you should rename all <tt>AES_*</tt> names. Assuming you are using <tt>MYLIB</tt> as a prefix the following <tt>sed</tt> should do the job.
 <pre>sed -i 's/OPENSSL/MYLIB/g' aes_armv4.h aes_armv4.S

@@ Line 296: / Line 296: @@
      return 0;
 }</pre>
 ==Benchmarks==

@@ Line 20: / Line 20: @@
 cp ./openssl/crypto/perlasm/arm-xlate.pl ./cryptogams/
 cp ./openssl/crypto/aes/asm/aes-armv4.pl ./cryptogams/
 cd cryptogams/</pre>

@@ Line 7: / Line 7: @@
 A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation operates in ECB mode and encrypts or decrypts full AES blocks. You are responsible for things like data alignment, padding and side channel counter-measures.
-At the moment older versions of Clang are miscompiling <tt>aes-armv4.S</tt>. Also see [https://bugs.llvm.org/show_bug.cgi?id=38133 LLVM Issue 38133].
+At the moment Clang is miscompiling <tt>aes-armv4.S</tt>. Also see [https://bugs.llvm.org/show_bug.cgi?id=38133 LLVM Issue 38133]. You can work around the problem by compiling <tt>aes-armv4.S</tt> with <tt>-mthumb</tt>, but all data must be aligned. If you don't use aligned buffers then a <tt>SIGBUS</tt> could occur.
 ==Obtain Source Files==