aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorEgor Tensin <Egor.Tensin@gmail.com>2015-06-20 21:24:16 +0300
committerEgor Tensin <Egor.Tensin@gmail.com>2015-06-20 21:24:16 +0300
commit963e36500a31dd151ed065dd9b4ce9bdca701693 (patch)
treee4b5c7a2efb3163316d60970ed82c2cf55d77c41
parentutils: README update (diff)
downloadaes-tools-963e36500a31dd151ed065dd9b4ce9bdca701693.tar.gz
aes-tools-963e36500a31dd151ed065dd9b4ce9bdca701693.zip
README updates
-rw-r--r--README.md2
-rw-r--r--test/README.md8
2 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index 0612be6..29a309a 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ To run programs that are using the AES-NI instruction set on a CPU w/o the suppo
[Intel Software Development Emulator](https://software.intel.com/en-us/articles/intel-software-development-emulator).
You can then run a program like this:
- > sde -- encrypt_block_aes.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
+ > sde -- aes_encrypt_block.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
69c4e0d86a7b0430d8cdb78070b4c55a
## Documentation
diff --git a/test/README.md b/test/README.md
index 28f1769..a10b13a 100644
--- a/test/README.md
+++ b/test/README.md
@@ -1,20 +1,20 @@
# Testing
-After you've [built](https://github.com/egor-tensin/aesni#building) the block encryption/decryption utilities, you can verify the implementation either manually or automatically using test vectors.
+After you've [built](https://github.com/egor-tensin/aesni#building) the block encryption/decryption utilities, you can verify the implementation either [manually](#manually) or [automatically](#using-test-vectors) using test vectors.
## Manually
-You can test the AES implementation using the block encryption/decryption utilities `encrypt_block_aes.exe` and `decrypt_block_aes.exe`.
+You can test the AES implementation using the block encryption/decryption utilities `aes_encrypt_block.exe` and `aes_decrypt_block.exe`.
Use the `--help` option to examine the usage info of a utility.
For example, for AES-128 in ECB mode:
- > encrypt_block_aes.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
+ > aes_encrypt_block.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
69c4e0d86a7b0430d8cdb78070b4c55a
and for AES-192 in CBC mode:
- > decrypt_block_aes.exe -a aes192 -m cbc -- 8e73b0f7da0e6452c810f32b809079e562f8ead2522c6b7b 000102030405060708090a0b0c0d0e0f 4f021db243bc633d7178183a9fa071e8 b4d9ada9ad7dedf4e5e738763f69145a 571b242012fb7ae07fa9baac3df102e0 08b0e27988598881d920a9e64f5615cd
+ > aes_decrypt_block.exe -a aes192 -m cbc -- 8e73b0f7da0e6452c810f32b809079e562f8ead2522c6b7b 000102030405060708090a0b0c0d0e0f 4f021db243bc633d7178183a9fa071e8 b4d9ada9ad7dedf4e5e738763f69145a 571b242012fb7ae07fa9baac3df102e0 08b0e27988598881d920a9e64f5615cd
6bc1bee22e409f96e93d7e117393172a
ae2d8a571e03ac9c9eb76fac45af8e51
30c81c46a35ce411e5fbc1191a0a52ef