We Need wallet address of 7 months for clean transactions, traceable on
Blockchain,
Ratio 45%/45%/10%
Sender/Reciever/Mandate
Telegram sender: @Arik_loader
On Thu, Nov 2, 2023, 7:25 PM Catherine Issabel
wrote:
>
> $500 million dollars available only for good and trusted receiver or
> mandate
>
$500 million dollars available only for good and trusted receiver or
mandate
Kindly contact the sender for more information:+1 (336) 345-9681
On Friday, May 12, 2023 at 7:09:38 PM UTC+1 Jeffrey Walton wrote:
> On Fri, May 12, 2023 at 1:09 PM Dwight Kulkarni
> wrote:
> >
> > Update: It seems
On Fri, May 12, 2023 at 1:09 PM Dwight Kulkarni wrote:
>
> Update: It seems to be an issue with CFB mode. If I switch to ECB: 12 ms to
> process the workload.
>
> in encrypt aes
> Encrypted 1at: 05/12/2023 17:06:54.838
> Encrypted 2at: 05/12/2023 17:06:54.838
> Encrypted 3at: 05/12/2023
*Update: It seems to be an issue with CFB mode. If I switch to ECB: 12 ms
to process the workload.*
in encrypt aes
Encrypted 1at: 05/12/2023 17:06:54.838
Encrypted 2at: 05/12/2023 17:06:54.838
Encrypted 3at: 05/12/2023 17:06:54.838
returning cipher
Encrypted 4at: 05/12/2023 17:06:54.850
BTW,
Are there any flags I should be setting when compiling the .a library into
my .exe to set the ARM acceleration ?
This is the makefile output:
*aarch64-poky-linux-g++ -mcpu=cortex-a53 -march=armv8-a+crc+crypto
-fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat
-Wformat-security
Hi Jeff,
The time is taken up all on the one line:
StringSource ss(message, true, new StreamTransformationFilter(e, new
StringSink(cipher)));
*Do you know what might be the difference versus the .exe test ?
AES/CFB (128-bit key)ARMv83444.991.1352044*
Encrypted 1at: 05/12/2023
On Fri, May 12, 2023 at 10:48 AM Dwight Kulkarni wrote:
>
> The new library is much faster, but I am still not getting that speed in the
> code. 1 second to encrypt 5 mb versus 3 seconds before.
>
> I added the .reserve(...) code also.
Well, you should profile your code to find the bottlenecks.
Two others:
string get_curr_datetime_str(){
return datetime_to_str(chrono::system_clock::now());
}
string datetime_to_str(std::chrono::high_resolution_clock::time_point
utctime){
std::chrono::high_resolution_clock::time_point::duration tt = utctime.
time_since_epoch();
const time_t durs =
I didn't give the load_aes_key functionhere it is :
std::pair load_aes_key_from_b64_str(string bkey,
string biv){
SecByteBlock key;
SecByteBlock iv;
try {
AutoSeededRandomPool prng;
key = SecByteBlock(udp_aes_key_size_in_bytes);
iv = SecByteBlock(udp_aes_key_iv_in_bytes);
Hi Jeff,
The new library is much faster, but I am still not getting that speed in
the code. 1 second to encrypt 5 mb versus 3 seconds before.
*I added the .reserve(...) code also.*
Start at: 05/12/2023 14:46:39.358
Start Encrypted at: 05/12/2023 14:46:39.607
in encrypt aes
returning
On Fri, May 12, 2023 at 10:27 AM Dwight Kulkarni wrote:
>
> These are the results from CryptoPP 8.7 vs 8.1 earlier:
> [...]
> AES/CFB (128-bit key)ARMv83444.991.1352044
> [...]
5 MB / 344 MB/s = 0.01453 s = 14/53 ms. That is below 200 ms.
Jeff
--
You received this message because you are
*These are the results from CryptoPP 8.7 vs 8.1 earlier:*
root@imx8mpevk:~/p2p_sockets# ./cryptest.exe b 2 1.8
Speed Comparison of Popular Crypto Algorithms
table {border-collapse: collapse;}
table, th, td, tr {border: 1px solid black;}
http://www.cryptopp.com;>Crypto++ 8.7.0
Hi Jeff,
I am using an ARM64 cross compiler. I source into the sdk using:
*source
/opt/fsl-imx-xwayland/5.10-hardknott/environment-setup-cortexa53-crypto-poky-linux*
I compile it on x86 and the move it to the embedded machine for testing.
This is the compiler command when I issue the make
On Fri, May 12, 2023 at 9:09 AM Dwight Kulkarni wrote:
>
> See below benchmark test results:
>
> root@imx8mpevk:~/p2p_sockets# ./cryptest.exe b 2 1.8
> [...]
> AES/CTR (128-bit key)C++6327.30.8861595
> AES/CTR (192-bit key)C++5531.30.8821587
> AES/CTR (256-bit key)C++4935.20.9101637
> AES/CBC
Hi Jeff,
See below benchmark test results:
root@imx8mpevk:~/p2p_sockets# ./cryptest.exe b 2 1.8
Speed Comparison of Popular Crypto Algorithms
table {border-collapse: collapse;}
table, th, td, tr {border: 1px solid black;}
http://www.cryptopp.com;>Crypto++ 8.1.0 Benchmarks
Here are
On Thu, May 11, 2023 at 4:24 PM Dwight Kulkarni wrote:
>
> I created a 5 MB message and encrypted it. The message takes 3 seconds to
> encrypt. I needed something around 200 ms, even if the encryption is weaker.
>
> My code is below, should I be setting any flags when compiling the library to
>
16 matches
Mail list logo
