[Bug 3466] Prefer using AEAD algorithms

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=3466

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net

--- Comment #6 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to tim from comment #4)
> AES_CGM doesn't much slower than AES_CTR

This varies a lot depending on the platform.  For a counterexample
(Ryzen 3900X), GCM is  half the speed:

$ openssl speed -evp aes-256-gcm
Doing AES-256-GCM for 3s on 16 size blocks: 103804564 AES-256-GCM's in
2.99s
Doing AES-256-GCM for 3s on 64 size blocks: 58949992 AES-256-GCM's in
2.99s
Doing AES-256-GCM for 3s on 256 size blocks: 34661021 AES-256-GCM's in
3.00s
Doing AES-256-GCM for 3s on 1024 size blocks: 11774310 AES-256-GCM's in
2.99s
Doing AES-256-GCM for 3s on 8192 size blocks: 1690281 AES-256-GCM's in
2.99s
Doing AES-256-GCM for 3s on 16384 size blocks: 853186 AES-256-GCM's in
3.00s

$ openssl speed -evp aes-256-ctr
Doing AES-256-CTR for 3s on 16 size blocks: 167022187 AES-256-CTR's in
2.99s
Doing AES-256-CTR for 3s on 64 size blocks: 131872734 AES-256-CTR's in
3.00s
Doing AES-256-CTR for 3s on 256 size blocks: 70440642 AES-256-CTR's in
2.99s
Doing AES-256-CTR for 3s on 1024 size blocks: 23978238 AES-256-CTR's in
3.00s
Doing AES-256-CTR for 3s on 8192 size blocks: 3358652 AES-256-CTR's in
2.99s
Doing AES-256-CTR for 3s on 16384 size blocks: 1703078 AES-256-CTR's in
3.00s

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.