crypto updated and optimized

I've updated the RSA, bigInt, and session key routines again. This is in preparation for the first official release. See the changelog at the end of crypto2.htm for details. Crypto.js is getting pretty stable. The remaining issues are (a) do we need a passphrase for the private key, and (b) do I need to use a better random number generator (ie higher entropy) for generating keys. I think the answers are (a) no and (b) yes, but I'm not sure yet. A better RNG will only mean changing crypto2.htm and not crypto.js. Putting a passphrase on the private key will mean changing the interface to rsaDecode again.

If you have an opinion, let me know. :-)

john