From 54f5a652e5bd9a04fdd3105f6f111b83f6443198 Mon Sep 17 00:00:00 2001 From: kokke Date: Fri, 1 Dec 2017 01:22:50 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2649912..57285e2 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ void AES_CTR_xcrypt_buffer(uint8_t* output, uint8_t* input, uint32_t length, con ``` -You can choose to use one or both of the modes-of-operation, by defining the symbols CBC, CTR or ECB. See the header file for clarification. +You can choose to use any of the modes-of-operation, by defining the symbols CBC, CTR or ECB. See the header file for clarification. There is no built-in error checking or protection from out-of-bounds memory access errors as a result of malicious input. The two functions AES_ECB_xxcrypt() do most of the work, and they expect inputs of 128 bit length.