crypto-sodium VS crypto-numbers

Compare crypto-sodium vs crypto-numbers and see what are their differences.

crypto-numbers

DEPRECATED - use cryptonite - Cryptographic number related function and algorithms (by vincenthz)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
crypto-sodium crypto-numbers
- 1
15 5
- -
4.0 0.0
4 months ago about 9 years ago
Haskell Haskell
Mozilla Public License 2.0 BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

crypto-sodium

Posts with mentions or reviews of crypto-sodium. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning crypto-sodium yet.
Tracking mentions began in Dec 2020.

crypto-numbers

Posts with mentions or reviews of crypto-numbers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-12.
  • Rolling your own crypto: Everything you need to build AES from scratch
    5 projects | news.ycombinator.com | 12 Jul 2022
    But you're approaching it from the wrong perspective: the idea isn't to use the crypto you implement yourself, the idea is to gain a better understanding of how the "magic" works. Of course my hand-rolled RSA/AES crypto is breakable, I know that because that's the default assumption.

    It's akin to saying, "you're not allowed to build your own smoke detector because it will be unsafe!". Of course I know that, I want to understand the differences between a photoelectric and ionization smoke detector, how they work in practice, because reading some PDF schematics just doesn't cut it for me.

    I honestly don't understand the line of reasoning of all this crypto gatekeeping.

    Fun fact: while I was doing my crypto deep dive in 2015, my language of choice being Haskell, I found issues in several libraries, specifically around entropy, and even one library with modulo bias [1]. They were acknowledged and addressed. It was a super fun learning exercise, and seeing all these comments how it's supposedly almost illegal to do this misses the point of people exploring and learning in their own ways.

    https://github.com/vincenthz/hs-crypto-numbers/commit/bceb54...

What are some alternatives?

When comparing crypto-sodium and crypto-numbers you can also consider the following projects:

nettle - nettle bindings for haskell

secp256k1 - Haskell bindings for secp256k1 library

crypto-rng - Cryptographic random number generator.

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

ripple - Implementation of Ripple client protocol in Haskell

elocrypt - Generate easy-to-remember, hard-to-guess passwords

crypto-api - Haskell generic interface (type classes) for cryptographic algorithms

crypto-pubkey - DEPRECATED - use cryptonite - Cryptographic public key related algorithms in haskell (RSA,DSA,DH,ElGamal)

keccak - Keccak hash functions

cryptoconditions - Interledger Crypto-Conditions in Haskell

ecdsa - ECDSA stuff in Haskell