@omegajs/flock-secret-stream
v1.0.0
Published
This package facilitates a secure stream, underpinned by the Noise protocol framework and libsodium's secretstream for robust cryptographic operations.
Downloads
2
Readme
@omegajs/flock-secret-stream
See the full API docs at docs.l1fe.tech/omega
Secret stream backed by Noise and libsodium's secretstream
Install Via L1FE's NPM
npm config set registry https://npm.l1fe.tech
npm install @omegajs/flock-secret-stream
Install Via L1FE's Git Repository
git clone https://lab.l1fe.tech/omega/flock-secret-stream.git
cd flock-secret-stream
npm install
Usage
You can either make a secret stream from an existing transport stream.
const SecretStream = require('@omegajs/flock-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!>
})
API
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,
hash,
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. Note: If one side calls s.setKeepAlive()
and the other does not, then the empty messages will be passed through to the piped stream.
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.
keyPair = SecretStream.keyPair([seed])
Generate a ed25519 key pair.
License
Apache-2.0