Good morning slackland, following with the plan I started a simple draft
for JavaScript (
https://github.com/abstractj/cryptoparty-js) we have
several alternatives outside there the most popular are Crypto-js
(
https://code.google.com/p/crypto-js/) and the Stanford crypto library
(
http://crypto.stanford.edu/sjcl/).
Before I finish the whole implementation I have some questions:
- Currently crypto-js doesn't have support for GCM or ECC, but sjcl has.
That's the reason why my choice was sjcl instead of crypto-js, but if
you have another good alternative, let me know.
- Create wrappers or not? If you read the unit tests at first glance (at
least for me) looks like is too much. Most part of developers are
looking for security by default. My idea is not to hide the library, but
provide a simple interface like:
Crypto crypto = new Crypto;
ciphertext = crypto. encrypt("blah");
crypto.decrypt(ciphertext);
Advanced users looking for another kind of algorithm/implementation or
whatever would still be able to make use of the plain and straight
crypto library.
- What is the best way to package this library? Bower?
Thoughts?
--
abstractj