Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
@hyperswarm/secret-stream
Advanced tools
Secret stream backed by Noise and libsodium's secretstream
npm install @hyperswarm/secret-stream
You can either make a secret stream from an existing transport stream.
const SecretStream = require('@hyperswarm/secret-stream')
const a = new SecretStream(true, tcpClientStream)
const b = new SecretStream(false, tcpServerStream)
// pipe the underlying rawstreams together
a.write(Buffer.from('hello encrypted!'))
b.on('data', function (data) {
console.log(data) // <Buffer hello encrypted!>
})
Or by making your own pipeline
const a = new SecretStream(true)
const b = new SecretStream(false)
// pipe the underlying rawstreams together
a.rawStream.pipe(b.rawStream).pipe(a.rawStream)
a.write(Buffer.from('hello encrypted!'))
b.on('data', function (data) {
console.log(data) // <Buffer hello encrypted!>
})
const s = new SecretStream(isInitiator, [rawStream], [options])
Make a new stream. isInitiator
is a boolean indication whether you are the client or the server.
rawStream
can be set to an underlying transport stream you want to run the noise stream over.
Options include:
{
pattern: 'XX', // which noise pattern to use
remotePublicKey, // set if your handshake requires it
keyPair: { publicKey, secretKey },
handshake: { // if you want to use an handshake performed elsewhere pass it here
tx,
rx,
handshakeHash,
publicKey,
remotePublicKey
}
}
The SecretStream returned is a Duplex stream that you use as as normal stream, to write/read data from, except it's payloads are encrypted using the libsodium secretstream.
Note that this uses ed25519 for the handshakes per default.
If need to load the key pair asynchronously, then secret-stream also supports passing in a promise
instead of the keypair that later resolves to { publicKey, secretKey }
. The stream lifecycle will wait
for the resolution and auto destroy the stream if the promise errors.
s.start(rawStream, [options])
Start a SecretStream from a rawStream asynchrously.
const s = new SecretStream({
autoStart: false // call start manually
})
// ... do async stuff or destroy the stream
s.start(rawStream, {
... options from above
})
s.setTimeout(ms)
Set the stream timeout. If no data is received within a ms
window,
the stream is auto destroyed.
s.setKeepAlive(ms)
Send a heartbeat (empty message) every time the socket is idle for ms
milliseconds.
keyPair = SecretStream.keyPair([seed])
Generate a ed25519 key pair.
s.publicKey
Get the local public key.
s.remotePublicKey
Get the remote's public key.
Populated after open
is emitted.
s.handshakeHash
Get the unique hash of this handshake.
Populated after open
is emitted.
s.on('connect', onconnect)
Emitted when the handshake is fully done. It is safe to write to the stream immediately though, as data is buffered internally before the handshake has been completed.
MIT
FAQs
Secret stream backed by Noise and libsodium's secretstream
The npm package @hyperswarm/secret-stream receives a total of 1,820 weekly downloads. As such, @hyperswarm/secret-stream popularity was classified as popular.
We found that @hyperswarm/secret-stream demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.