Can AES/GCM mode encrypt in-place? I'd like the input and output buffers
to be roughly the same (referring to the same allocated region, up to an
offset), so that if I'm encrypting 16MB at a time, I don't have to allocate
16MB x 2 to hold the intermediate result. In the example AES/GCM Crypto++
AEAD code I downloaded a while back, I noticed a construction like:
AuthenticatedEncryptionFilter ef (e, new StringSink (cipher), false,
(TAG_SIZE))
Is it just as easy to let the output go into an existing (C) buffer? If so
I'm wondering what minimal constructs are needed to use an existing buffer
(instead of a new StringSink ...)? For the in-place property, is it
possible to specify the output of the encryption to be a few cryptographic
blocks before the unencrypted input? If I am to share the same buffer for
input and output, then I would intentionally allocate additional bytes at
the start (or possibly the end) to serve as scratch space and output space.
I'm wondering what overlaps are allowable and which are not.
Also, is it possible and practical to use the Serpent cipher instead of
AES, operating in the GCM encryption mode?
Finally, I'm having trouble viewing wiki pages on cryptolounge.org. For
example, the following page:
http://www.cryptolounge.org/wiki/GCM
is now blank when I view it in Google Chrome or Firefox. I get the same
result with other cryptolounge.org pages. Is there something I'm missing?
Is there a backup Wiki or is the content available elsewhere?
--
--
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.
---
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].
For more options, visit https://groups.google.com/d/optout.
