| Server IP : 199.250.214.225 / Your IP : 3.135.193.144 Web Server : Apache System : Linux vps64074.inmotionhosting.com 3.10.0-1160.105.1.vz7.214.3 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : nicngo5 ( 1001) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /home/nicngo5/funds.upgrade.nicn.gov.ng/funds-upgraded/node_modules/browserify-aes/ |
Upload File : |
# browserify-aes [](https://travis-ci.org/crypto-browserify/browserify-aes) Node style aes for use in the browser. Implements: - createCipher - createCipheriv - createDecipher - createDecipheriv - getCiphers In node.js, the `crypto` implementation is used, in browsers it falls back to a pure JavaScript implementation. Much of this library has been taken from the aes implementation in [triplesec](https://github.com/keybase/triplesec), a partial derivation of [crypto-js](https://code.google.com/p/crypto-js/). `EVP_BytesToKey` is a straight up port of the same function from OpenSSL as there is literally no documenation on it beyond it using 'undocumented extensions' for longer keys. ## LICENSE [MIT](LICENSE)