We wanted to be able to write Javascript that used crypto on both the client and the server but we did not want to rely on Javascript implementations of crypto. The only native cryptography availible in browser is Web Crypto, this resulted in us creating a node-webcrypto-ossl
a native polyfil for WebCrypto based on Openssl.
At this time this solution should be considered suitable for research and experimentation, further code and security review is needed before utilization in a production application.
git clone https://github.com/PeculiarVentures/node-webcrypto-ossl
cd node-webcrypto-ossl
npm install
mocha
To use KeyStorage you shoud init WebCrypto with directory
option. If directory
option is missing then keyStorage
is null
var WebCrypto = require("node-webcrypto-ossl");
var webcrypto = new WebCrypto({
directory: "key_storage"
})
KeyStorage implements interface of W3 Storage
var keyStorage = webcrypto.keyStorage;
// generating RSA key
webcrypto.subtle.generateKey({
name: "RSASSA-PKCS1-v1_5",
modulusLength: 1024,
publicExponent: new Uint8Array([1, 0, 1]),
hash: {
name: "SHA-1"
}
},
false,
["sign", "verify"]
)
.then(function(keyPairs){
/**
* saving private RSA key to KeyStorage
* creates file ./key_storage/prvRSA-1024.json
*/
keyStorage.setItem("prvRSA-1024", keyPairs.privateKey);
})
To get key from KeyStorage
var rsaKey = webcrypto.getItem("prvRSA-1024");
The threat model is defined in terms of what each possible attacker can achieve.
TODO: ADD ASSUMPTIONS
TODO: ADD THREATS FROM HANCOCK SERVICE COMPROMISE
TODO: ADD THREATS FROM WEAK CRYPTOGRAPHY
TODO: ADD THREATS FOR IMPROPER USE OF CRYPTOGRAPHY
Please report bugs either as pull requests or as issues in the issue tracker. node-webcrypto-ossl has a full disclosure vulnerability policy. Please do NOT attempt to report any security vulnerability in this code privately to anybody.