On Fri, May 12, 2023 at 1:09 PM Dwight Kulkarni <[email protected]> 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 17:06:54.838 > returning cipher > Encrypted 4at: 05/12/2023 17:06:54.850
Yeah, CFB mode is a hard mode in software. The software is effectively providing a linear feedback shift register, and it does a lot of [non-accelerated] bit twiddling. That's why it needs 4+ cycles to process a byte. I think you would have better results with GCM mode. First, GCM mode is an authenticated encryption mode, so you get authenticity assurances over the ciphertext. Second, you get hardware acceleration with both the bulk cipher encryption (AES), and the mac over the ciphertext (GMAC). Also see https://www.cryptopp.com/wiki/Authenticated_Encryption . Jeff -- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/CAH8yC8n5na5bkfkM6fUJ2cRfwpEBvxFquPMidsm4_GPVsaidAg%40mail.gmail.com.
