From e907196101af48cd3f40b40c36c7778589fd79d8 Mon Sep 17 00:00:00 2001 From: Frank Denis Date: Wed, 30 Jul 2014 22:42:53 -0700 Subject: [PATCH] Do not recommend AES128 over AES256. --- src/libsodium/include/sodium/crypto_stream_aes256estream.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/libsodium/include/sodium/crypto_stream_aes256estream.h b/src/libsodium/include/sodium/crypto_stream_aes256estream.h index d4978345..27331d31 100644 --- a/src/libsodium/include/sodium/crypto_stream_aes256estream.h +++ b/src/libsodium/include/sodium/crypto_stream_aes256estream.h @@ -7,9 +7,8 @@ * provide any security against active attacks. * Furthermore, this implementation was not part of NaCl. * - * If you are looking for a stream cipher, you might consider - * crypto_stream_aes128ctr, crypto_stream_chacha20 or crypto_stream_(x)salsa20 - * which are timing-attack resistant. + * If you are looking for a stream cipher, you might consider crypto_stream_chacha20 + * or crypto_stream_(x)salsa20 which are timing-attack resistant instead. * * But unless you know what you're doing, what you are looking for is probably * the crypto_box or crypto_secretbox functions.