[cryptopp-users] Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
Hi all, I have my RSA encrypt function as below. I compile my program with the following: g++ -g -c -static -pthread -I../ -I/data/prj/external-libs/include/cryptopp/ ../src/threading/server.cpp g++ -g ../lbin/*.o -static -pthread -o server -L/data/prj/external-libs/lib/ -l:libcryptopp.a

[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
Further info: *without -static*, this is the output from the remote server: broker got data of size 512 Broker handler thread started... 512 first two bytes are 128 and 198 and 154 *clear text begins with 68 180 -->> this should be 00 02* Either no 00 02 beginning block or no

[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
Hi all: ldd ./server compiled without the -static flag shows following .so dependencies. Since the -static flag will add the same libraries as .a form, it will compile a slightly different version. I am trying to think why the encryption would produce two different results, maybe something

[cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Dwight Kulkarni
I got it working by implementing the raw Integer method. See my code below, previous encryption is commented out. I don't know why but it wasn't working otherwise and *I think it has something to do with memory allocation maybe it works with -static flag because some references are staying in

[cryptopp-users] Re: crypto++ library error

2023-04-25 Thread Jeffrey Walton
On Monday, April 10, 2023 at 10:26:42 PM UTC-4 bv...@ganpatuniversity.ac.in wrote: Hi everyone, I had included crypto library function in my file. When I run the file it shows some error as following: Integer’ was not declared in this scope; did you mean ‘CryptoPP::Integer’? Can anyone please

Re: [cryptopp-users] Re: Strange behavior with -static compilation flag

2023-04-25 Thread Jeffrey Walton
On Tue, Apr 25, 2023 at 7:12 PM Dwight Kulkarni wrote: > > I got it working by implementing the raw Integer method. See my code below, > previous encryption is commented out. I don't know why but it wasn't working > otherwise and I think it has something to do with memory allocation maybe it >

[cryptopp-users] Re: AES ARM slow on M1

2023-04-25 Thread Jeffrey Walton
On Friday, March 31, 2023 at 1:44:41 AM UTC-4 Sam Van Gucht wrote: Hi everyone, We noticed AES GCM in significant slower on M1 compare to an Intel Mac. Encrypting a 100mb files takes ~130ms on Intel Mac & while on M1 it takes ~510ms. Are the ARMv8 Cryptographic instructions not supported