On Friday, July 6, 2018 at 4:02:40 AM UTC-4, 许皓宇 wrote:
>
> Thanks for your reply:)
> Maybe a warning or auto checker is better for someone who do not know
> details of AES-CTR like me
>
I believe the mode objects throw when the iv length is not correct for the
cipher:
$ cat test.cxx
Regardless, I agree that enforcing specified IV length would be a desirable
property and a useful enhancement.
Sent from my test iPhone
> On Jul 6, 2018, at 04:04, Weikeng Chen wrote:
>
> I think crypto libraries have to assume the developers to have some
> familiarity with the cryptography
I think crypto libraries have to assume the developers to have some
familiarity with the cryptography and use it properly.
For example, why do you use AES-CTR? It does not provide integrity guarantee.
Today, AES-GCM is a commonly better option.
On Fri, Jul 6, 2018 at 1:02 AM, 许皓宇 wrote:
>
Thanks for your reply:)
Maybe a warning or auto checker is better for someone who do not know
details of AES-CTR like me
在 2018年7月6日星期五 UTC+8下午2:38:01，Weikeng Chen写道：
>
> The following code in modes.h
> (https://github.com/weidai11/cryptopp/blob/master/modes.h#L300) shows
> that IV will
The following code in modes.h
(https://github.com/weidai11/cryptopp/blob/master/modes.h#L300) shows
that IV will become BLOCKSIZE.
CipherModeFinalTemplate_CipherHolder(const byte *key, size_t length,
const byte *iv)
{
this->m_cipher = >m_object;
this->SetKey(key, length,
On Friday, July 6, 2018 at 2:23:00 AM UTC-4, 许皓宇 wrote:
>
> I've used cryptopp in my project recently, i try to use AES-CTR model
> encryption.
>
> CryptoPP::CTR_Mode::Encryption(const CryptoPP::byte* key,
> size_t length, const CryptoPP::byte* iv)
>
> This constructor provide a length check
