You are indeed correct. However, the access violation was happening deep inside the crypto++ library. Ideally, you should be able to throw anything at the library and it should capture all bad inputs, rather than getting access violations or unhandled exceptions - of course, very difficult to achieve but a worthy aim. Having said this, I still think the library is excellent.
On Mar 30, 6:06 pm, Geoff Beier <[email protected]> wrote: > On Tue, Mar 30, 2010 at 10:32, Alan Cooper <[email protected]> > wrote: > > I used the cryptest example as a template for my development and my > > RSA decryption was failing because I wasn't initialising the global > > RNG. It would be good if a nice exception can be thrown instead of an > > access violation. Not sure how easy it is to make such a change? > > The "global RNG" is part of the code you copied as a template, not > part of the library itself. So you can, of course throw whatever type > of exception you'd like before attempting to use it. > > Geoff -- 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. To unsubscribe, reply using "remove me" as the subject.
