Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
@libp2p/crypto
Advanced tools
Crypto primitives for libp2p
crypto.aes
crypto.hmac
crypto.keys
crypto.keys.generateKeyPair(type, bits)
crypto.keys.generateEphemeralKeyPair(curve)
crypto.keys.keyStretcher(cipherType, hashType, secret)
crypto.keys.marshalPublicKey(key, [type])
crypto.keys.unmarshalPublicKey(buf)
crypto.keys.marshalPrivateKey(key, [type])
crypto.keys.unmarshalPrivateKey(buf)
crypto.keys.import(encryptedKey, password)
privateKey.export(password, format)
crypto.randomBytes(number)
crypto.pbkdf2(password, salt, iterations, keySize, hash)
$ npm i @libp2p/crypto
<script>
tagLoading this module through a script tag will make it's exports available as Libp2pCrypto
in the global namespace.
<script src="https://unpkg.com/@libp2p/crypto/dist/index.min.js"></script>
This repo contains the JavaScript implementation of the crypto primitives needed for libp2p. This is based on this go implementation.
const crypto = require('libp2p-crypto')
// Now available to you:
//
// crypto.aes
// crypto.hmac
// crypto.keys
// etc.
//
// See full API details below...
The libp2p-crypto
library depends on the Web Crypto API in the browser. Web Crypto is available in all modern browsers, however browsers restrict its usage to Secure Contexts.
This means you will not be able to use some libp2p-crypto
functions in the browser when the page is served over HTTP. To enable the Web Crypto API and allow libp2p-crypto
to work fully, please serve your page over HTTPS.
crypto.aes
Exposes an interface to AES encryption (formerly Rijndael), as defined in U.S. Federal Information Processing Standards Publication 197.
This uses CTR
mode.
crypto.aes.create(key, iv)
key: Uint8Array
The key, if length 16
then AES 128
is used. For length 32
, AES 256
is used.iv: Uint8Array
Must have length 16
.Returns Promise<{decrypt<Function>, encrypt<Function>}>
decrypt(data)
data: Uint8Array
Returns Promise<Uint8Array>
encrypt(data)
data: Uint8Array
Returns Promise<Uint8Array>
const crypto = require('libp2p-crypto')
// Setting up Key and IV
// A 16 bytes array, 128 Bits, AES-128 is chosen
const key128 = Uint8Array.from([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15])
// A 16 bytes array, 128 Bits,
const IV = Uint8Array.from([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15])
async function main () {
const decryptedMessage = 'Hello, world!'
// Encrypting
const cipher = await crypto.aes.create(key128, IV)
const encryptedBuffer = await cipher.encrypt(Uint8Array.from(decryptedMessage))
console.log(encryptedBuffer)
// prints: <Uint8Array 42 f1 67 d9 2e 42 d0 32 9e b1 f8 3c>
// Decrypting
const decipher = await crypto.aes.create(key128, IV)
const decryptedBuffer = await cipher.decrypt(encryptedBuffer)
console.log(decryptedBuffer)
// prints: <Uint8Array 42 f1 67 d9 2e 42 d0 32 9e b1 f8 3c>
console.log(decryptedBuffer.toString('utf-8'))
// prints: Hello, world!
}
main()
crypto.hmac
Exposes an interface to the Keyed-Hash Message Authentication Code (HMAC) as defined in U.S. Federal Information Processing Standards Publication 198. An HMAC is a cryptographic hash that uses a key to sign a message. The receiver verifies the hash by recomputing it using the same key.
crypto.hmac.create(hash, secret)
hash: String
secret: Uint8Array
Returns Promise<{digest<Function>}>
digest(data)
data: Uint8Array
Returns Promise<Uint8Array>
Example:
const crypto = require('libp2p-crypto')
async function main () {
const hash = 'SHA1' // 'SHA256' || 'SHA512'
const hmac = await crypto.hmac.create(hash, uint8ArrayFromString('secret'))
const sig = await hmac.digest(uint8ArrayFromString('hello world'))
console.log(sig)
}
main()
crypto.keys
Supported Key Types
The generateKeyPair
, marshalPublicKey
, and marshalPrivateKey
functions accept a string type
argument.
Currently the 'RSA'
, 'ed25519'
, and secp256k1
types are supported, although ed25519 and secp256k1 keys support only signing and verification of messages. For encryption / decryption support, RSA keys should be used.
crypto.keys.generateKeyPair(type, bits)
type: String
, see Supported Key Types above.bits: Number
Minimum of 1024Returns Promise<{privateKey<Uint8Array>, publicKey<Uint8Array>}>
Generates a keypair of the given type and bitsize.
crypto.keys.generateEphemeralKeyPair(curve)
curve: String
, one of 'P-256'
, 'P-384'
, 'P-521'
is currently supportedReturns Promise
Generates an ephemeral public key and returns a function that will compute the shared secret key.
Focuses only on ECDH now, but can be made more general in the future.
Resolves to an object of the form:
{
key: Uint8Array,
genSharedKey: Function
}
crypto.keys.keyStretcher(cipherType, hashType, secret)
cipherType: String
, one of 'AES-128'
, 'AES-256'
, 'Blowfish'
hashType: String
, one of 'SHA1'
, SHA256
, SHA512
secret: Uint8Array
Returns Promise
Generates a set of keys for each party by stretching the shared key.
Resolves to an object of the form:
{
k1: {
iv: Uint8Array,
cipherKey: Uint8Array,
macKey: Uint8Array
},
k2: {
iv: Uint8Array,
cipherKey: Uint8Array,
macKey: Uint8Array
}
}
crypto.keys.marshalPublicKey(key, [type])
key: keys.rsa.RsaPublicKey | keys.ed25519.Ed25519PublicKey | keys.secp256k1.Secp256k1PublicKey
type: String
, see Supported Key Types above. Defaults to 'rsa'.Returns Uint8Array
Converts a public key object into a protobuf serialized public key.
crypto.keys.unmarshalPublicKey(buf)
buf: Uint8Array
Returns RsaPublicKey|Ed25519PublicKey|Secp256k1PublicKey
Converts a protobuf serialized public key into its representative object.
crypto.keys.marshalPrivateKey(key, [type])
key: keys.rsa.RsaPrivateKey | keys.ed25519.Ed25519PrivateKey | keys.secp256k1.Secp256k1PrivateKey
type: String
, see Supported Key Types above.Returns Uint8Array
Converts a private key object into a protobuf serialized private key.
crypto.keys.unmarshalPrivateKey(buf)
buf: Uint8Array
Returns Promise<RsaPrivateKey|Ed25519PrivateKey|Secp256k1PrivateKey>
Converts a protobuf serialized private key into its representative object.
crypto.keys.import(encryptedKey, password)
encryptedKey: string
password: string
Returns Promise<PrivateKey>
Converts an exported private key into its representative object. Supported formats are 'pem' (RSA only) and 'libp2p-key'.
privateKey.export(password, format)
password: string
format: string
the format to export to: 'pem' (rsa only), 'libp2p-key'Returns string
Exports the password protected PrivateKey
. RSA keys will be exported as password protected PEM by default. Ed25519 and Secp256k1 keys will be exported as password protected AES-GCM base64 encoded strings ('libp2p-key' format).
crypto.randomBytes(number)
number: Number
Returns Uint8Array
Generates a Uint8Array with length number
populated by random bytes.
crypto.pbkdf2(password, salt, iterations, keySize, hash)
password: String
salt: String
iterations: Number
keySize: Number
in byteshash: String
the hashing algorithm ('sha1', 'sha2-512', ...)Computes the Password Based Key Derivation Function 2; returning a new password.
Feel free to join in. All welcome. Open an issue!
This repository falls under the IPFS Code of Conduct.
Licensed under either of
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
FAQs
Crypto primitives for libp2p
We found that @libp2p/crypto demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.