[cryptopp-users] New wiki pages: HC-128 and Rabbit

2018-07-06 Thread Jeffrey Walton
Hi Everyone, There are some new wiki pages on HC-128, HC-256 and Rabbit stream ciphers. They are part of eSTREAM portfolio, Phase 3 (final), Profile 1 (software). * https://www.cryptopp.com/wiki/HC-128 * https://www.cryptopp.com/wiki/Rabbit I also updated ChaCha, Salsa and Sosemanuk so

Re: [cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread Jeffrey Walton
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

[cryptopp-users] Re: Algorithm::AlgorithmProvider member function

2018-07-06 Thread Jeffrey Walton
On Monday, July 2, 2018 at 1:57:12 AM UTC-4, Jeffrey Walton wrote: > > Hi Everyone, > > I've got a branch that added an algorithm provider. It can be used for > benchmarks like https://www.cryptopp.com/test-bench.html . The change > is modest and shown at https://pastebin.com/ekr9VUaN . >

Re: [cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread Uri Blumenthal
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

Re: [cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread Weikeng Chen
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: >

Re: [cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread 许皓宇
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

Re: [cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread Weikeng Chen
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,

[cryptopp-users] Re: IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread Jeffrey Walton
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

[cryptopp-users] IV checker for CryptoPP::CTR_Mode::Encryption()

2018-07-06 Thread 许皓宇
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 of key but do not check length of iv e.g. if i use an iv with not