diff options
| author | Egor Tensin <Egor.Tensin@gmail.com> | 2015-06-10 14:57:24 +0300 |
|---|---|---|
| committer | Egor Tensin <Egor.Tensin@gmail.com> | 2015-06-10 14:57:24 +0300 |
| commit | f80ba09a00b207e1dbcaa3fd2a6f967c60663775 (patch) | |
| tree | cda5c6ac71ee9addcaae9c26c4f217d45bddfeb9 /test/README.md | |
| parent | code style (diff) | |
| download | aes-tools-f80ba09a00b207e1dbcaa3fd2a6f967c60663775.tar.gz aes-tools-f80ba09a00b207e1dbcaa3fd2a6f967c60663775.zip | |
test: README update
Diffstat (limited to 'test/README.md')
| -rw-r--r-- | test/README.md | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/test/README.md b/test/README.md index 5bb437a..8bfe479 100644 --- a/test/README.md +++ b/test/README.md @@ -11,26 +11,26 @@ For the ECB mode of operation, the usage is: and - aesNNNecb_decrypt_block.exe KEY [CIPHER...] [-- KEY1 [PLAIN1--]...] + aesNNNecb_decrypt_block.exe KEY0 [CIPHER0...] [-- KEY1 [CIPHER1--]...] where `NNN` is either `128`, `192` or `256`. For the modes of operation involving initialization vectors (CBC, CFB, OFB, CTR, etc.), use the utilities like this: - aesNNNxxx_encrypt.exe KEY0 IV0 [PLAIN0...] [-- KEY1 IV1 [PLAIN1...]...] + aesNNNxxx_encrypt_block.exe KEY0 IV0 [PLAIN0...] [-- KEY1 IV1 [PLAIN1...]...] and - aesNNNxxx_decrypt.exe KEY0 IV0 [CIPHER0...] [-- KEY1 IV1 [CIPHER1...]...] + aesNNNxxx_decrypt_block.exe KEY0 IV0 [CIPHER0...] [-- KEY1 IV1 [CIPHER1...]...] -where `NNN` is the same. +where `NNN` is the same and `xxx` is either `cbc`, `cfb`, `ofb`, `ctr` or some other mode of operation. For example, - > aes128ecb_encrypt.exe 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff + > aes128ecb_encrypt_block.exe 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff 69c4e0d86a7b0430d8cdb78070b4c55a - > aes192cbc_encrypt.exe 000102030405060708090a0b0c0d0e0f1011121314151617 1032547698badcfe1032547698badcfe 00112233445566778899aabbccddeeff 00112233445566778899aabbccddeeff 00112233445566778899aabbccddeeff + > aes192cbc_encrypt_block.exe 000102030405060708090a0b0c0d0e0f1011121314151617 1032547698badcfe1032547698badcfe 00112233445566778899aabbccddeeff 00112233445566778899aabbccddeeff 00112233445566778899aabbccddeeff 92c01276b27eb8baaa3cabe2c661d4a8 d42bdf90c1a48221a92a5137c1445418 96248fca82fbefa31345ae7d8fb7933e @@ -39,8 +39,7 @@ On older CPUs, you can run the utilities [using Intel SDE](https://github.com/eg ## Using test vectors -The test scripts are written in Python 3, hence you need to be able to run Python 3 scripts in order to use them. -The scripts have uniform interfaces: they accept a path to the directory with the block encryption/decryption utilities and allow to run them [using Intel SDE](https://github.com/egor-tensin/aesni#running-on-older-cpus). +The test scripts are written in Python 3 and have uniform interfaces: they accept a path to the directory with the block encryption/decryption utilities and allow to run them [using Intel SDE](https://github.com/egor-tensin/aesni#running-on-older-cpus). They also write log files with a short summary at the end. In general, each scripts counts the number of tests that failed, succeeded, caused an error, and the tests that were skipped. You must therefore make sure that @@ -55,7 +54,7 @@ Use `--help` to see the script's usage details. ### NIST Special Publication 800-38A -To test the implementation against the vectors from [NIST Special Publication 800-38A](http://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf) using `800-32a.py`. +To test the implementation against the vectors from [NIST SP 800-38A](http://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf) using `800-32a.py`. python 800-38a.py -r C:\build\test\Debug |