Displaying 1 to 13 from 13 results

tweetnacl-js - Port of TweetNaCl cryptographic library to JavaScript

Port of TweetNaCl / NaCl to JavaScript for modern browsers and Node.js. Public domain.The primary goal of this project is to produce a translation of TweetNaCl to JavaScript which is as close as possible to the original C implementation, plus a thin layer of idiomatic high-level API on top of it.

libsodium.js - libsodium compiled to Webassembly and pure JavaScript, with convenient wrappers

The sodium crypto library compiled to WebAssembly and pure Javascript using Emscripten, with automatically generated wrappers to make it easy to use in web applications. The complete library weights 188 Kb (minified, gzipped, includes pure js + webassembly versions) and can run in a web browser as well as server-side.

minisign - A dead simple tool to sign files and verify digital signatures.

Minisign is a dead simple tool to sign files and verify signatures. Minisign uses the EdDSA signature system, and deterministic signature schemes are fragile against fault attacks. However, conducting these requires physical access or the attacker having access to the same physical host.

ed2curve-js - Convert Ed25519 signing keys into Curve25519 Diffie-Hellman keys

Convert Ed25519 signing key pair into Curve25519 key pair suitable for Diffie-Hellman key exchange. This means that by exchanging only 32-byte Ed25519 public keys users can both sign and encrypt with NaCl.Note that there's currently no proof that this is safe to do. It is safer to share both Ed25519 and Curve25519 public keys (their concatenation is 64 bytes long).

exonum-client - JavaScript client for Exonum blockchain

Compatible with Exonum v0.5. A JavaScript library to work with Exonum blockchain from browser and Node.js. Used to sign transactions before sending to blockchain and verify blockchain responses using cryptographic proofs. Contains numerous helper functions.


Chloride is a Cryptography Library (Cl) for javascript enviroments.chloride is a compatibility layer that gives you bindings to libsodium when used in node.js, and either the libsodium-wrappers which is libsodium compiled to javascript via emscripten if performance is important but code size isn't. Or, if you are not doing many crypto operations, it uses tweetnacl, which is a handwritten port, and 1/10 the size of libsodium-wrappers.

huffin - Vanity ed25519 public keys, through Huffman Codes

Human-readable representation of ed25519 public keys, through Huffman Codes.This software is licensed under the MIT License.

emojilock - minilock ids represented as emoji

converts minilock ids, e.g.into base-emoji representations, e.g.

bittorrent-dht-store-keypair - create and load signing keys for bittorrent-dht dht_store

Setting up elliptic curve keys and signing properly for BEP44 can be tricky, especially since bittorrent uses the more obscure supercop/ref10 instead of sodium/nacl ed25519 key formatting.Sign a buffer or string value with the private key.

ed25519-supercop - ed25519 curve operations using a supercop/ref10 implementation

This module provides C++ bindings for orlp/ed25519 (formerly nightcracker/ed25519).supercop implementations use the same algorithm but different key formatting than sodium/nacl keys.

curve25519-js - Curve25519 Javascript Implementation

Ed25519-like signatures with X25519 keys, Axolotl-style.Functions accept and return bytes as Uint8Arrays.

passphrase-identity - Regenerable ed25519 keys for OpenSSH and OpenPGP.

Regenerable ed25519 keys for OpenSSH and OpenPGP. Passphrase Identity allows you to deterministically generate ed25519 key pairs (signing keys) for OpenSSH and OpenPGP from a set of parameters. This allows you to (re)generate your key pair on a computer which, for example, lacks persistent storage - it derives an "identity" from a passphrase.

hs-ed25519 - Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation.

This package implements minimal bindings to the ed25519 signature scheme. It's designed to be small, with no dependencies, and fast. It also comes with extensive guidelines and detailed documentation. It should be relatively easy to both depend on directly with Cabal or even copy into any projects that need it directly. For full details (including notes on the underlying implementation), check out the docs.