The devil is in the details. I think Pat is making a reasonable point...without a minimum-compilable segment of code it is impossible to say what MIGHT be causing a problem. Looking at a snippet I might ASSUME you are setting parameters that you have missed, simply because "of course" you have to set the key val. what one programmer assumes "everyone knows" may be the one peice of information another programmer most needs. -Mike
-----Original Message----- From: Guy Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: Re: CBC_Mode<AES> giving me grief What I was shooting for here was whether there is anything obviously wrong with my code -- that is, whether I'm conceptually correct in how I'm using Crypto++. What you're asking for is more along the lines of detailed debugging, which I would never ask anyone else to do -- it's my job to deal with that. I feel bad enough taking up your time to just read these emails; having somebody actually try to solve my problem for me is too much. If I could get an asnwer like "yes, this code *should* work" or "no, it's clearly wrong, you need to set an IV first" I would be able to go the rest of the way. A sanity check is what I'm really looking for. Thanks for the offer, though. --Guy ----- Original Message ----- From: "Pat Deegan" <[EMAIL PROTECTED]> To: "CryptoPP" <[EMAIL PROTECTED]> Sent: Thursday, July 10, 2003 4:07 PM Subject: Re: CBC_Mode<AES> giving me grief > Greets, > > On Thu, 2003-07-10 at 15:34, Guy Smith wrote: > > The code snippet below is roughly what I'm doing, although > > doesn't appear together in the actual program. > > I'd be glad to help if I can... > > I normally like to play with the code in order to ensure my answer is > valid - but there's a limit to how much clean up I'll do... Your code > fragment demonstrates what your attempting but is hardly usable (it > won't compile without a lot of extra work removing references to > irrelevant objects, definining variables etc) - perhaps you could > include the minimum code that reproduces the error and can actually be > compiled? > > Thanks, > -- > Pat Deegan, > http://www.psychogenic.com/ > PGP: http://www.keyserver.net 0x03F86A50 >
