summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkokke <spam@rowdy.dk>2015-11-10 00:34:07 +0100
committerkokke <spam@rowdy.dk>2015-11-10 00:34:07 +0100
commitdf3dde5feabe9e41c01695638180e4e25749aed1 (patch)
tree3c0d240d7a7cb19de704dad5fc5e8bd8828a37f9
parentUpdate README.md (diff)
downloadtiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar.gz
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar.bz2
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar.lz
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar.xz
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.tar.zst
tiny-AES-c-df3dde5feabe9e41c01695638180e4e25749aed1.zip
-rw-r--r--README.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/README.md b/README.md
index 07ffbb9..3071ccb 100644
--- a/README.md
+++ b/README.md
@@ -2,8 +2,7 @@
This is a small and portable implementation of the AES128 ECB and CBC encryption algorithms written in C.
-This is meant to be the back-end of whatever error checking you need to validate your input.
-There is no built-in protection for buffer overflows if malicious input is given, or the size of buffers are not chosen carefully.
+There is no built-in error checking or protection from out-of-bounds memory access errors as a result of malicious input.
The API is very simple and looks like this (I am using C99 `<stdint.h>`-style annotated types):