npm-packages
/
rpclibrary
Watch 1
Star 0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
Tree: 41a5d14fd8
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '41a5d14fd8'
${ noResults }
rpclibrary/node_modules/crypto-browserify
Daniel Hübleitner 615619e6e7 start werk 5 years ago
..
example start werk 5 years ago
test start werk 5 years ago
.travis.yml start werk 5 years ago
.zuul.yml start werk 5 years ago
LICENSE start werk 5 years ago
README.md start werk 5 years ago
index.js start werk 5 years ago
package.json start werk 5 years ago

README.md

crypto-browserify

A port of node’s crypto module to the browser.

Build Status js-standard-style Sauce Test Status

The goal of this module is to reimplement node’s crypto module, in pure javascript so that it can run in the browser.

Here is the subset that is currently implemented:

  • createHash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)
  • createHmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)
  • pbkdf2
  • pbkdf2Sync
  • randomBytes
  • pseudoRandomBytes
  • createCipher (aes)
  • createDecipher (aes)
  • createDiffieHellman
  • createSign (rsa, ecdsa)
  • createVerify (rsa, ecdsa)
  • createECDH (secp256k1)
  • publicEncrypt/privateDecrypt (rsa)
  • privateEncrypt/publicDecrypt (rsa)

todo

these features from node’s crypto are still unimplemented.

  • createCredentials

contributions

If you are interested in writing a feature, please implement as a new module, which will be incorporated into crypto-browserify as a dependency.

All deps must be compatible with node’s crypto (generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the browser. see sha.js

Crypto is extra serious so please do not hesitate to review the code, and post comments if you do.

License

MIT