npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

signal-identity-tools

v0.0.2

Published

identity generation and management tools for the Signal protocol

Downloads

5

Readme

signal-identity-tools

npm install signal-identity-tools

[WIP]

a keyserver and id generation tools for the signal-protocol

Build Status

example

see example.js for a starting point.

the example does not cover uploading new unsignedPreKeys, or replacing signedPreKeys. see API for details.

(eventually this will all be wrapped in a friendlier way).

todos & cavaeats

  • No rate-limiting or access control on PreKey fetches
    • This is necessary to make sure people don't deplete your one-time prekeys
  • No validating uploaded keys (yet)
  • The keyserver is just an API
    • You can wrap it in your own transport layer (HTTP, WS, etc)

api

let idtools = require('signal-identity-tools/idtools')

idtools.freshIdentity(keyId, store, cb)

keyId is a number.

store is a signal-protocol store (see signal-protocol).

Calls back on (err, { complete, sanitized, store }).

complete is the full identity, with secret keys. sanitized is the public-facing version, ready to send to the keyserver.

The store this method returns is the same store you pass in. I return it so you will notice that I am mutating it.

idtools.newSignedPreKey(identity, keyId, store, cb)

Like freshIdentity, calls back on (err, { complete, sanitized, store } )

sanitized is the public-facing version, ready to send to the keyserver.

idtools.newUnsignedPreKeys(n, keyId, cb)

Creates n unsigned (one-time) PreKeys.

Calls back on (err, { complete, sanitized } ), where both complete and sanitized are lists of keys of length n.

sanitized is the public-facing version, ready to send to the keyserver.

let keyserver = require('signal-identity-tools/keyserver')

ks = keyserver(level)

level is a leveldb-like instance.

You will want to configure your level db's encoding a bit, to allow for typed arrays:

// utilities for setting up level instances
var msgpack = require('msgpack-lite')
let valueEncoding = {encode: msgpack.encode,
                     decode: msgpack.decode,
                     buffer: true}
let level = require('level')
let opts = {valueEncoding: valueEncoding}
let db = level('/tmp/myKeyserverDb', opts)

ks.register(name, publicID, cb)

Registers a new username name, where publicID comes from the callback value of idtools.freshIdentity's .sanitized

cb(err)

ks.preKeyBundle(name, cb)

Calls back on the keyserver's next PreKeyBundle for a user name, per signal-protocol's spec for these bundles.

b(err, bundle)

ks.replaceSignedPreKey(name, signedPreKey, cb)

In the Signal protocol, users should replace their signed PreKeys occasionally.

This registers a new Signed PreKey for name, name, where signedPreKey comes from the callback value of idtools.newSignedPreKey's .sanitized.

cb(err)

ks.uploadUnsignedPreKeys(name, unisgnedPreKeys, cb)

In the Signal protocol, users must upload unsigned PreKeys regularly.

This uploads new, unsigned (one-time) PreKeys for name name, where unsignedPreKeys come from the callback value of idtools.newUnsignedPreKeys's .sanitized.

cb(err)

license

BSD