On Wed, Jun 04, 2003 at 09:38:24PM -0400, Pat Deegan wrote: > 1) Should I really be using RSASS<PKCS1v15, SHA>? What other options do > I have and where can I go to compare them?
Well, with Crypto++, you have a really large number of options. Unless you know what you're doing, I'd stay with RSASS<PKCS1v15, SHA> because that is the most commonly used in the industry. If you want to find out what the other options are and how to compare them, I suggest joining the IEEE P1363 mailing list, which will give you access to the current draft P1363 standard. The standard is a wealth of information, and most of the public key algorithms in Crypto++ come from it. Go to http://links.cryptopp.com and follow the appropriate link from there. The Crypto++ online reference manual should also have links to SCAN (Standard Cryptographic Algorithm Naming) entries, which should in turn have references to the original papers and analysis. > 2) I've been using the CryptoPP::BlockingRng and it has been, well, > blocking. This happens when I attempt to make multiple consecutive > signatures. I assume it is waiting on more entropy - is this correct? > Can I just use the non blocking version, if so then what is it "costing" > me? I suggest using AutoSeededRandomPool instead, and specify the option of seeding it with the blocking RNG. Using the non-blocking RNG means that the random numbers you get may not be of sufficient entropy. > 3) Who owns the pointers? There's a *lot* of code like: This is documented in Readme.txt.
