Hi Eugene, Perfect! I coded up a test after reading your post. I my case, I am transferring the file, so I just need a one time verification before handing it off to the backend processor.
I appreciate the heads up! Thanks Again, Gerry On Apr 22, 4:26 pm, Eugene Zolenko <[email protected]> wrote: > > I meant saving a copy without the hash. > > > Okay, if I understand correctly, passing a FileSink etc. to > > HashVerificationFilter with the PUT_MESSAGE flag set, the resulting > > output will be just the original file/message without the hash? > > > If so, that's exactly what I was talking about. Sorry. I didn't > > realize that from looking at the docs. I did find it odd that it would > > have been left out though. > > Yep, that example would do exactly what you want. If you don't want it > to throw exceptions, you'll have to own HashVerificationFilter > yourself, and pass it into source via redirector and then check > HashVerificationFilter::GetLastResult(). > > You also can use the file right after verifying, in the same filter > chain depending on what you do with it, you might not want to cut off > the hash and instead verify on every read. --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
