Hi Mouse,

Were you doing something similar to "byte key [16]"? Same with the IV
- except the IV is the size of a block. I always use the Crypto++
defines. If so, this is the first thing I would correct. Sorry - a lot
of code has been flying past lately.

Jeff

On 9/27/07, Mouse <[EMAIL PROTECTED]> wrote:
>
> > Without seeing the code that doesn't work (i.e. precisely
> > what you're doing to "reverse" the process), it's hard to say
> > why it doesn't work for you. If you simply don't give the
> > StreamTransformationFilter an attachment, though, it behaves
> > exactly as you wish.
>
> I understand what you're saying. You're right, and your new example helps.
>
> The funny thing is - my decrypting program dumps core on the last line of
> the following block of code:
>
>  CBC_Mode<AES>::Decryption decrAES(aesDKey, 32, aesDIV);
>  SecByteBlock recbytes;
>  StreamTransformationFilter *aesD =
>    new StreamTransformationFilter(decrAES);
>  FileSource fs("tenc.txt", true, new Base64Decoder(aesD));
>
>
> The example you've given below makes perfect sense. I'm tryng to think along
> the same lines. For some reasons I just can't establish that connection with
> FileSource...
>
> > StreamTransformationFilter * outfilt = new
> >    StreamTransformationFilter(decryptor);
> > FileSource outgoing(encfile.c_str(), true, new
> >    Base64Decoder(outfilt));
>
> Here's where my code coredumps... My debugging is unsuccessful, I'm getting
> "No stack" with Backtrace...
>
> > The loop at the end is a silly example, but I think it shows
> > how to do what you want.
>
> Yes it does. Now I need to figure out why that line dumps core (and why that
> dump seems un-analyzable).

--~--~---------~--~----~------------~-------~--~----~
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.
-~----------~----~----~----~------~----~------~--~---

Reply via email to