sodium.cr
tweetnacl-js
Our great sponsors
| sodium.cr | tweetnacl-js | |
|---|---|---|
| - | 3 | |
| 46 | 1,721 | |
| - | - | |
| 0.0 | 2.9 | |
| almost 2 years ago | about 2 months ago | |
| Crystal | JavaScript | |
| MIT License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sodium.cr
We haven't tracked posts mentioning sodium.cr yet.
Tracking mentions began in Dec 2020.
tweetnacl-js
-
I am considering adding Skiff as an encrypted email provider and would like community feedback
On cryptography, our whitepaper shares information on the general cryptography choices - login, authentication, keypairs, etc. It's quite similar to password managers or encrypted communication apps. In the actual product (code here https://github.com/skiff-org/skiff-mail), we use the library TweetNaCl (https://github.com/dchest/tweetnacl-js) which is designed to be fast, trustworthy, and performant
-
Ask HN: Should I learn the tech behind crypto even if I don't want to own any?
Working with encryption more broadly will equip you to understand the fundamentals that underpin the web3/crypto world: hashes, asymmetric crypto, signatures, signature chains, etc. And it also has many uses, of course, outside the web3 realm.
If you're working with Node, tweetnacl.js (https://github.com/dchest/tweetnacl-js) gives you secure defaults and a nice API to start learning and building with.
Once you're familiar with this stuff, blockchains/cryptocurrency/web3 loses a lot of its mystery. They're essentially all just different takes on using key management and signature chains to verify identities and
-
A Hold'em Poker game in Clojure
Those things are not the same. With the Berne Convention Implementation Act of 1988 (and the earlier Copyright Act of 1976, which went into effect in 1978), all works were by default copyright protected. In the absence of a legal notice, nobody can reliably use this for anything at all. Most jurisdictions don't even have a way of reliably dedicating anything to the public domain, hence the existence of permissive licenses. Please at least consider adding the ISC or MIT or Unlicense text or similar to a LICENSE or NOTICE file in your repository. An example: https://github.com/dchest/tweetnacl-js/blob/master/LICENSE
What are some alternatives?
crystal-sha3 - An SHA-3 implementation written in Crystal.
auth-jwt - A demo to learn JWT by reverse engineering
cmac - Crystal implementation of the Cipher-based Message Authentication Code (CMAC)
hazedumper - up to date csgo offsets and hazedumper config
monocypher.cr - Crystal bindings for Monocypher
examples
ChaCha20-BLAKE2b - Committing ChaCha20-BLAKE2b, XChaCha20-BLAKE2b, and XChaCha20-BLAKE2b-SIV AEAD implementations.
skiff-apps - Privacy-first, end-to-end encrypted Mail, Pages, Drive, and Calendar.
Halite - High-level cryptography interface powered by libsodium
js-jose - JavaScript library to encrypt/decrypt data in JSON Web Encryption (JWE) format and to sign/verify data in JSON Web Signature (JWS) format. Leverages Browser's native WebCrypto API.
orion - Usable, easy and safe pure-Rust crypto [Moved to: https://github.com/orion-rs/orion]
RbNaCl - Ruby FFI binding to the Networking and Cryptography (NaCl) library (a.k.a. libsodium)