crypto-js README

The project's README from github.com/brix/crypto-js. As one markdown file: README.md.

crypto-js

JavaScript library of crypto standards.

Discontinued

Active development of CryptoJS has been discontinued. This library is no longer maintained.

Nowadays, NodeJS and modern browsers have a native Crypto module. The latest version of CryptoJS already uses the native Crypto module for random number generation, since Math.random() is not crypto-safe. Further development of CryptoJS would result in it only being a wrapper of native Crypto. Therefore, development and maintenance has been discontinued, it is time to go for the native crypto module.

Node.js (Install)

Requirements:

npm install crypto-js

Usage

ES6 import for typical API call signing use case:

import sha256 from 'crypto-js/sha256';
import hmacSHA512 from 'crypto-js/hmac-sha512';
import Base64 from 'crypto-js/enc-base64';

const message, nonce, path, privateKey; // ...
const hashDigest = sha256(nonce + message);
const hmacDigest = Base64.stringify(hmacSHA512(path + hashDigest, privateKey));

Modular include:

var AES = require("crypto-js/aes");
var SHA256 = require("crypto-js/sha256");
...
console.log(SHA256("Message"));

Including all libraries, for access to extra methods:

var CryptoJS = require("crypto-js");
console.log(CryptoJS.HmacSHA1("Message", "Key"));

Client (browser)

Requirements:

bower install crypto-js

Usage

Modular include:

require.config({
    packages: [
        {
            name: 'crypto-js',
            location: 'path-to/bower_components/crypto-js',
            main: 'index'
        }
    ]
});

require(["crypto-js/aes", "crypto-js/sha256"], function (AES, SHA256) {
    console.log(SHA256("Message"));
});

Including all libraries, for access to extra methods:

// Above-mentioned will work or use this simple form
require.config({
    paths: {
        'crypto-js': 'path-to/bower_components/crypto-js/crypto-js'
    }
});

require(["crypto-js"], function (CryptoJS) {
    console.log(CryptoJS.HmacSHA1("Message", "Key"));
});

Usage without RequireJS

<script type="text/javascript" src="path-to/bower_components/crypto-js/crypto-js.js"></script>
<script type="text/javascript">
    var encrypted = CryptoJS.AES(...);
    var encrypted = CryptoJS.SHA256(...);
</script>

API

See: https://cryptojs.gitbook.io/docs/

AES Encryption

Plain text encryption

var CryptoJS = require("crypto-js");

// Encrypt
var ciphertext = CryptoJS.AES.encrypt('my message', 'secret key 123').toString();

// Decrypt
var bytes  = CryptoJS.AES.decrypt(ciphertext, 'secret key 123');
var originalText = bytes.toString(CryptoJS.enc.Utf8);

console.log(originalText); // 'my message'

Object encryption

var CryptoJS = require("crypto-js");

var data = [{id: 1}, {id: 2}]

// Encrypt
var ciphertext = CryptoJS.AES.encrypt(JSON.stringify(data), 'secret key 123').toString();

// Decrypt
var bytes  = CryptoJS.AES.decrypt(ciphertext, 'secret key 123');
var decryptedData = JSON.parse(bytes.toString(CryptoJS.enc.Utf8));

console.log(decryptedData); // [{id: 1}, {id: 2}]

List of modules

Release notes

4.2.0

Change default hash algorithm and iteration's for PBKDF2 to prevent weak security by using the default configuration.

Custom KDF Hasher

Blowfish support

4.1.1

Fix module order in bundled release.

Include the browser field in the released package.json.

4.1.0

Added url safe variant of base64 encoding. 357

Avoid webpack to add crypto-browser package. 364

4.0.0

This is an update including breaking changes for some environments.

In this version Math.random() has been replaced by the random methods of the native crypto module.

For this reason CryptoJS might not run in some JavaScript environments without native crypto module. Such as IE 10 or before or React Native.

3.3.0

Rollback, 3.3.0 is the same as 3.1.9-1.

The move of using native secure crypto module will be shifted to a new 4.x.x version. As it is a breaking change the impact is too big for a minor release.

3.2.1

The usage of the native crypto module has been fixed. The import and access of the native crypto module has been improved.

3.2.0

In this version Math.random() has been replaced by the random methods of the native crypto module.

For this reason CryptoJS might does not run in some JavaScript environments without native crypto module. Such as IE 10 or before.

If it's absolute required to run CryptoJS in such an environment, stay with 3.1.x version. Encrypting and decrypting stays compatible. But keep in mind 3.1.x versions still use Math.random() which is cryptographically not secure, as it's not random enough.

This version came along with CRITICAL BUG.

DO NOT USE THIS VERSION! Please, go for a newer version!

3.1.x

The 3.1.x are based on the original CryptoJS, wrapped in CommonJS modules.

crypto-js (brix/crypto-js)

Searching Database…

16.4K ·GitHub
Crypto-js
What is this?Crypto-js is a JavaScript library of crypto standards — hashes, ciphers like AES, PBKDF2 key derivation and encodings such as Base64, usable from Node.js and the browser.
Is this for Node.js or for the browser?Both — it is a plain library, not a service. In Node.js you install it with npm; the README shows Bower as the package manager for frontend clients, and you can import modules individually or include everything at once.
How do I get it into my project?In Node.js install it with npm and use ES6 imports for the modules you need. In the browser add it via Bower with modular includes, include all libraries for extra methods, or use the build that works without RequireJS.
Will it run in older browsers or environments like React Native?Version 4.x needs the native crypto module for random number generation, so it may not run in environments without one, such as IE 10 or before or React Native. The 3.1.x line runs there but uses Math.random(), which is not crypto-safe.
Is CryptoJS still maintained?No. Active development has been discontinued and the library is no longer maintained; the author recommends moving to the native Crypto module built into NodeJS and modern browsers.
What algorithms does it include?The API section covers AES encryption for plain text and objects. Release notes also mention PBKDF2 — whose weak defaults were hardened in 4.2.0 — plus Blowfish support and a custom KDF hasher added in the same release.
Why did development stop?Because NodeJS and modern browsers now ship a native Crypto module, and recent CryptoJS versions already use it for random number generation. Continued development would have turned CryptoJS into just a wrapper of that native module.
Are there versions I should avoid?Yes — 3.2.0 shipped with a critical bug and the README says DO NOT USE THIS VERSION. Also, 3.1.x still relies on Math.random(), which is not random enough for cryptographic use, although its encrypt/decrypt output stays compatible with newer versions.
What are similar projects?hashsigs-ts, javascript-obfuscator, CyberChef, q, gun, validator.js, zxcvbn, hashsigs-solidity
Which topics is it in?hashing, cryptography, javascript-library, encryption, deprecated, browser, security, npm, frontend, nodejs, library, javascript
Creator
brix
Size
10.8 MB
Stars
16.4K
Updated
CommitOct 24
Age
13y
Commits · 90 Days