With some larger payloads (448 bytes and 896 bytes) and using the release build (opps) I'm seeing ~30 Mbits/sec. Getting better but still very far from what's advertised.
On Aug 26, 11:20 am, kt <[email protected]> wrote: > I'm running the aes-gcm example project and I am putting a timer > around the following chunk of code in the main line (which as far as I > can tell captures the aes-gcm encoding): > > AuthenticatedEncryptionFilter ef( e, > new StringSink( cipher ), false, TAG_SIZE > ); // AuthenticatedEncryptionFilter > > // AuthenticatedEncryptionFilter::ChannelPut > // defines two channels: "" (empty) and "AAD" > // channel "" is encrypted and authenticated > // channel "AAD" is authenticated > ef.ChannelPut( "AAD", (const byte*)adata.data(), adata.size > () ); > ef.ChannelMessageEnd("AAD"); > > // Authenticated data *must* be pushed before > // Confidential/Authenticated data. Otherwise > // we must catch the BadState exception > ef.ChannelPut( "", (const byte*)pdata.data(), pdata.size() ); > ef.ChannelMessageEnd(""); > > I'm seeing a performance of just under 1 Mbits/sec (using the > hardcoded test vector of 16 bytes of zero). This is a far cry from > the ~800 Mbits/sec advertised. Any ideas? > > thanks. > kt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
