aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorTravis Jensen <[email protected]>2011-05-06 12:36:38 -0600
committerSverker Eriksson <[email protected]>2011-05-18 15:44:47 +0200
commitb74ff4f6df28405222752fb2b1089f11e96e5406 (patch)
tree204553deb241de9e0ad24fb2133a2138a3d8c07c /README.md
parent2ef48dca9328e0b928117f21bc9ee6dbc5a614cc (diff)
downloadotp-b74ff4f6df28405222752fb2b1089f11e96e5406.tar.gz
otp-b74ff4f6df28405222752fb2b1089f11e96e5406.tar.bz2
otp-b74ff4f6df28405222752fb2b1089f11e96e5406.zip
Add true streaming AES (CTR) encryption and streaming HMAC operations
The current crypto module implementations require all of the data being encrypted or authenticated to be in memory at one time. When trying to encrypt or authenticate a large file (on order of GBs), this is problematic. The implementation of AES CTR uses the same underlying implementation as aes_ctr_[en|de]crypt, but hands the state back to the client after every operation. The HMAC implementation differs from the previous implementations of sha_mac and md5_mac. The old implementations did not utilize the OpenSSL HMAC implementation. In order to ensure that I didn't implement something incorrectly, I chose to use the OpenSSL HMAC implementation directly, since it handles streaming as well. This has the added side benefit of allowing other hash functions to be used as desired (for instances, I added support for ripemd160 hashing). While I haven't done this, it seems like the existing md5_mac and sha_mac functions could either be depricated or redefined in terms of the new hmac_ functions. Update AES CTR and HMAC streaming with code review input Ensure that memcpy operations in hmac operations are being size checked properly. Rename aes_ctr_XXX_with_state to aes_ctr_stream_XXX. Remove redundant hmac_init_[sha|md5|ripemd160] functions. Fix documentation for hmac_final_n. Fix possible error using negative value as a marker on an unsigned int Now, use a separate marker and add a unit test to test specifically for a case where HashLen is larger than the underlying resultant hash. Revert "Fix possible error using negative value as a marker on an unsigned int" This reverts commit 59cb177aa96444c0fd3ace6d01f7b8a70dd69cc9. Resolve buffer overflow posibility on an unsigned int. Change handling the marker for HashLen to use the fact that a second parameter that has to be the the HashLen was passed. Also, ensure that HashLen parameter is positive.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions