aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/test/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'test/README.md')
-rw-r--r--test/README.md22
1 files changed, 18 insertions, 4 deletions
diff --git a/test/README.md b/test/README.md
index cf12953..40e5580 100644
--- a/test/README.md
+++ b/test/README.md
@@ -1,15 +1,20 @@
# Testing
-After you've [built](../#building) the block encryption/decryption utilities,
-you can verify the implementation either [manually](#manually) or
+After you've [built](../README.md#building) the utilities, you can verify the
+implementation either [manually](#manually) or
[automatically](#using-test-vectors) using test vectors.
+Using the built utilities, you can also test
+[file encryption](#file-encryption).
+
## Manually
-You can test the AES implementation using the block encryption/decryption
-utilities `encrypt_block.exe` and `decrypt_block.exe`.
+You can test the implementation using the block encryption/decryption utilities
+`encrypt_block.exe` and `decrypt_block.exe`.
Use the `--help` option to examine the usage info of a utility.
+File encryption
+
For example, for AES-128 in ECB mode:
> encrypt_block.exe -a aes128 -m ecb -- 000102030405060708090a0b0c0d0e0f 00112233445566778899aabbccddeeff
@@ -60,3 +65,12 @@ To test the implementation against the vectors from
The AES Known Answer Test (KAT) Vectors are used and read from `KAT_AES.zip`.
python cavp.py -p C:\build\utils\Debug
+
+## File encryption
+
+You can also test file encryption using `file.py`.
+Its interface and output is similar to the
+[block encryption](#using-test-vectors) test scripts.
+The expected ciphertexts (for encryption) and plaintexts (for decryption),
+along with the keys and initialization vectors, are stored in the files under
+a separate directory (`file/` by default).