[cryptopp-users] New wiki page on ChaChaTLS

2019-01-24 Thread Jeffrey Walton
Hi Everyone, We added the IETF's version of ChaCha named ChaChaTLS. It is slightly different than Bernstein's original version. The IETF's version of ChaCha is specified in https://tools.ietf.org/html/rfc7539. ChaChaTLS is mostly the same as Bernstein's algorithm. A few of the differences

[cryptopp-users] Decrypt same encrypted data multiple times results in different data

2019-01-24 Thread Jeffrey Walton
#include "cryptlib.h" #include "rabbit.h" #include #include int main(int argc, char *argv[]) { using namespace CryptoPP; const uint8_t rabbitKey[16] = "012345678901234"; const uint8_t rabbitIV[8] = "0123456"; RabbitWithIV::Encryption enc; RabbitWithIV::Decryption dec;

Re: [cryptopp-users] Re: Using Crypto++ to sign using private key; SHA1 vs Whirlpool

2019-01-24 Thread Jeffrey Walton
On Thu, Jan 24, 2019 at 8:28 AM Olli Savolainen wrote: > > Oh thanks, that actually seems to work. I had just forgotten the using > directive so it seemed like SHA256 enum value didn't seem to work. > Just curious, why is SHA3 different, or have I just messed up somehow? It is probably you, but

Re: [cryptopp-users] Re: Using Crypto++ to sign using private key; SHA1 vs Whirlpool

2019-01-24 Thread Jeffrey Walton
On Thu, Jan 24, 2019 at 8:28 AM Olli Savolainen wrote: > > Oh thanks, that actually seems to work. I had just forgotten the using > directive so it seemed like SHA256 enum value didn't seem to work. > Just curious, why is SHA3 different, or have I just messed up somehow? > Anyway, can I help

[cryptopp-users] Re: Cryptopp unable to link with undefined reference to VTT for CryptoPP::RSAFunction

2019-01-24 Thread niz al
I have found the issue, it is because of this compilation flag : -flto As soon as I remove this compiling flag, everything works normal, please note that activating this flag which is: -flto : This option runs the standard link-time optimizer. When invoked with source code, it generates

[cryptopp-users] Re: Using Crypto++ to sign using private key; SHA1 vs Whirlpool

2019-01-24 Thread Olli Savolainen
On Thursday, January 24, 2019 at 2:58:54 PM UTC+2, Jeffrey Walton wrote: > > > > On Thursday, January 24, 2019 at 6:49:22 AM UTC-5, Olli Savolainen wrote: > >> >> Thanks. The enums available seem to be SHA1 and SHA3. >> Changing the enum value to SHA3 and the headers to match doesn't seem to

[cryptopp-users] Re: Cryptopp unable to link with undefined reference to VTT for CryptoPP::RSAFunction

2019-01-24 Thread Jeffrey Walton
On Thursday, January 24, 2019 at 5:31:07 AM UTC-5, niz al wrote: > > Hello, > > I'am using cryptopp on aarch64 (arm64 architecture system), I'am facing a > problem when compiling my binary which use cryptopp-7.0.0, the only link > problem I face is related to RSAFunction, all the other

[cryptopp-users] Re: Using Crypto++ to sign using private key; SHA1 vs Whirlpool

2019-01-24 Thread Jeffrey Walton
On Thursday, January 24, 2019 at 6:49:22 AM UTC-5, Olli Savolainen wrote: > > Thanks. The enums available seem to be SHA1 and SHA3. > Changing the enum value to SHA3 and the headers to match doesn't seem to > compile so apparently the example would need to be changed otherwise too. > How

[cryptopp-users] Re: Using Crypto++ to sign using private key; SHA1 vs Whirlpool

2019-01-24 Thread Olli Savolainen
On Thursday, January 24, 2019 at 12:08:05 AM UTC+2, Jeffrey Walton wrote: > > > > On Wednesday, January 23, 2019 at 11:09:49 AM UTC-5, Olli Savolainen wrote: >> >> Thank you Jeff. I appreciate it a lot. >> >> Basically I would like to convert the code in the first example (below) >> to use

[cryptopp-users] Cryptopp unable to link with undefined reference to VTT for CryptoPP::RSAFunction

2019-01-24 Thread niz al
Hello, I'am using cryptopp on aarch64 (arm64 architecture system), I'am facing a problem when compiling my binary which use cryptopp-7.0.0, the only link problem I face is related to RSAFunction, all the other classes worked perfectly, here is the program itself which is really a basic one