crypto.generateKeyPair(t) should have option to pass random seed data

[tarun1475]

Feature:-
crypto.generateKeyPair(type, options, callback)

The above method should have an option to pass 128 or 256 bits of random seed so that
everytime we give that seed to this function we will have the same private and public key pairs.

For applications which needs end to end encryption specifically in bitcoin space it is really helpful to create same keys from the bip39 mnemonic and use it for end to end encryption between various devices.

Alternatives :-
For now i am using https://github.com/VirgilSecurity/virgil-crypto this library for doing end to end encryption tasks.

In their public docs we are not able to find the exact method i am asking for but if we see their code base there is a method virgilCrypto.generateKeysFromKeyMaterial("STRING")

So it can be used as

const VirgilCrypto =require('virgil-crypto');
const bip39 = require('bip39');

const mnemonic = bip39.generateMnemonic();

const seed = bip39.mnemonicToSeedHex(mnemonic);

const virgilCrypto = new VirgilCrypto.VirgilCrypto();

const keyPair = virgilCrypto.generateKeysFromKeyMaterial(seed);

const privateKey = virgilCrypto.exportPrivateKey(keyPair.privateKey);
const publicKey = virgilCrypto.exportPublicKey(keyPair.publicKey);

I am looking to have same sort of method for nodejs crypto module.

Thanks

[bnoordhuis]

openssl doesn't support that so that kind of closes the discussion. You should open an issue with them first if you want to see this happen.

That said, knowing how openssl works internally, I don't think it's a feature they could add easily. All keygen operations pull from a global entropy pool.

[jasnell]

ah, crap, that's right. That's a bit unfortunate.