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

@futuretense/ed25519-box

v1.0.1

Published

Simple public-key encryption for nodejs and browsers

Downloads

13

Readme

@futuretense/ed25519-box

Simple public-key encryption for nodejs and browsers

Draws inspiration from box of NaCl, but works with ed25519 keys right away.

ed25519-box vs nacl-box

  • ed25519-box uses ed25519 key-pairs directly, whereas w/ nacl-box you have to transform ed25519 keys to curve25519 keys.
  • ed25519-box gives you the choice of not using authentication, whereas nacl-box always adds a Poly1305 authentication tag.
  • ed25519-box uses standard crypto APIs, already included in node.js, or in your browser -- no extra dependencies

Installation

npm install @futuretense/ed25519-box

Usage

import { encrypt, decrypt } from '@futuretense/ed25519-box';

Functions

Encrypt

async encrypt(privKey, pubKey, input, nonce, authenticate = true);

|Parameter|Type|Description| |:--|:--|:--| |privKey|Uint8Array|The private key of the sender| |pubKey|Uint8Array|The public key of the recipient| |input|Uint8Array|The data to be encrypted| |nonce|Uint8Array|The message nonce| |authenticate|Boolean|Should it be authenticated?|

|Return value|Description| |:--|:--| |Promise<Uint8Array>|The encrypted data|

Decrypt

async decrypt(privKey, pubKey, input, nonce, authenticate = true);

|Parameter|Type|Description| |:--|:--|:--| |privKey|Uint8Array|The private key of the recipient| |pubKey|Uint8Array|The public key of the sender| |input|Uint8Array|The encrypted data| |nonce|Uint8Array|The message nonce| |authenticate|Boolean|Should it be authenticated?|

|Return value|Description| |:--|:--| |Promise<Uint8Array>|The decrypted data|

Authentication

Authenticated mode (which is the default) uses AES-256-GCM to add integrity control to the pot, to make it possible to verify that the provided cipher output has been encrypted by someone with access to the encryption key.

Authentication adds sixteen bytes of data to the output.

Un-authenticated mode uses AES in counter mode (AES-256-CTR), and doesn't add any extra data.

Nonce

Authenticated mode has a twelve byte nonce, and un-authenticated mode has a sixteen byte nonce.

In both modes, the nonces provided are used as initial values for the counters.

Nonce re-use

The idea is that, for a given key, you should consider each counter value as "burnt" whenever you use it. -- Thomas Pornin

Both modes use stream ciphers that divide the input data into 128-bit blocks, which are then exclusive-or:ed with the result of a function based on the encryption key and the counter value for a block.

If a (key, counter)-combination is ever used twice, this can be exploited to arrive at a block that's the exclusive-or of the two unencrypted input blocks.

Copyright © 2020 Future Tense, LLC