> Maybe the second param of FileSource (pumpAll) which is set 
> to true below should be made false? Then you can call Pump() 
> perhaps? And instead of a FileSink you might use an 
> ArraySink? Im just guessing here sorry :-)

Setting pumpAll to false causes (in my case) the file to report zero bytes
available, and providing zero bytes to my attempts to read from it.

ArraySink is a good idea - but it looks like it's just a one-dimensional
byte-string equivalent.

Perhaps Wei Dai could enlighten us all as to how to accomplish what I've
described below?

P.S. I've connected Base64Decoder to AES Decryptor by the construct shown
below.

string decipheredText;
StringSink ssd(decipheredText);
StreamTransformationFilter aesDec(decrAES, &ssd);
Base64Decoder b64dec(&aesDec);


> On 9/26/07, Mouse <[EMAIL PROTECTED]> wrote:
> >
> >
> > Let me ask a simpler question.  Here are the definitions:
> >
> > CBC_Mode<AES>::Decryption decrAES;
> > Base64Decoder b6d;
> >
> > My question is: how do I connect them into something like this:
> >
> > StreamTransformationFilter aesD(b6d, decrAES);
> >
> > The above line doesn't even compile (types are wrong) -
> > can you please suggest the correct types and constructs?
> >
> > Tnx!
> >
> > P.S. If then you could show how to connect the above aesD with 
> > FileSource - I'd be more than happy. :-)
> >
> > P.P.S.  A solution that does something like
> >   FileSource f("name", true, 
> > new Base64Decoder(new StreamTransformationFilter(decrAES, new 
> > FileSink("name2")))); 
> > is not acceptable for this application, sorry. 
> > Because it adds FileSink.
> >
> > P.P.P.S. Does crypto++ library require symmetry on both ends, i.e.
> > FileSource on one end must be paired with FileSink on the 
> > other?! At least one example that works for me seems to prove
> > that assumption wrong, but...
> >  > >
> >
> 
> 
> --
> "Thou shalt not follow the null pointer for at it's end 
> madness and chaos lie."


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