Oops, forgot a couple of things. This is with Crypto++ 5.0, compiling with MSVC 7 (without the .NET).
The problem didn't occur when using the previous version of Crypto++ ( I think I was using 4.2 before). ----- Original Message ----- From: "Rickey Braddam" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 9:08 AM Subject: Base 64 decoder > I think I have a problem: > > I put 76 bytes of ciphertext into the Base64 encoder, and get 104 bytes out, > the last two are "=" padding bytes. OK so far. > > I later put the 104 bytes into the Base64 decoder and get 77 bytes > MaxRetrievable.... looking at the StringSink there are actually two null > bytes following the ciphertext, neither of which were part of the original > ciphertext. > > I looked into the source code for the Base64 decoder, and its parent > classes, but keep getting wrapped around the axle with the defines you use > to "inject" code... > > I need to get 76 bytes out when I put 76 in... the decryption won't work > because I have a message IV and digest at fixed positions in the > ciphertext.... > > How can I fix this? > > Rick, [EMAIL PROTECTED] >
