newhope alternatives and similar packages
Based on the "Cryptography" category.
Alternatively, view newhope alternatives based on common mentions on social networks and blogs.
-
-
merkle-tree
An implementation of a Merkle Tree and merkle tree proofs -
-
pedersen-commitment
An implementation of Pedersen commitment schemes -
-
arithmetic-circuits
Arithmetic circuits for zero knowledge proof systems -
-
-
-
-
-
oblivious-transfer
Oblivious transfer for multiparty computation -
-
cryptohash
efficient and practical cryptohashing in haskell. DEPRECATED in favor of cryptonite -
-
elliptic-curve
A polymorphic interface for elliptic curve operations -
ed25519
Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation. -
cipher-aes
DEPRECATED - use cryptonite - a comprehensive fast AES implementation for haskell that supports aesni and advanced cryptographic modes. -
cipher-blowfish
DEPRECATED by cryptonite; A collection of cryptographic block and stream ciphers in haskell -
crypto-api
Haskell generic interface (type classes) for cryptographic algorithms -
signable
Deterministic serialisation and signatures with proto-lens and protobuf-elixir support -
-
-
skein
Skein, a family of cryptographic hash functions. Includes Skein-MAC as well. -
-
galois-fft
Finite field polynomial arithmetic based on fast Fourier transforms -
qnap-decrypt
Decrypt files encrypted by the QNAP's Hybrid Backup Sync -
cryptohash-sha256
Fast, pure and practical SHA-256 implementation -
-
crypto-pubkey-types
Crypto Public Key algorithm generic types. -
crypto-pubkey
DEPRECATED - use cryptonite - Cryptographic public key related algorithms in haskell (RSA,DSA,DH,ElGamal) -
-
cipher-aes128
Based on cipher-aes, but using a crypto-api interface and providing resulting IVs for each mode -
-
cprng-aes
Crypto Pseudo Random Number Generator using AES in counter mode -
crypto-enigma
A Haskell Enigma machine simulator with rich display and machine state details.
Clean code begins in your IDE with SonarLint
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of newhope or a related project?
|
Build time-series-based applications quickly and at scale.
sponsored
www.influxdata.com
|
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
This package provides a library for the NewHope key exchange protocol. It has been made via examination of the official NewHope project's public domain C reference code and the author is not affiliated with that team or with NIST.
This codebase has not yet been reviewed by anyone other than the author. Until such time as it has been competently reviewed, please consider it as a draft implementation only, and do not rely on it for actual security in practice. Judged by comparison with the reference library, it does produce correct results but could contain subtle (or obvious!) flaws. In addition, it has not been optimized for performance and at this stage is probably quite a bit slower than the reference C implementation on any given platform.
This project uses the build manager "stack" to produceː
Crypto.NewHope, a library intended for general use.PQCgenKAT-- a binary which generates KAT (Known Answer Test) files in the format required by the NIST PQC project. Invoke this binary with the single argument "all" to generate all of the KAT files.speed-- a binary which runs performance tests of some of the NewHope functionality. These tests correspond to largely equivalent tests in the reference NewHope C code.
In addition, the project contains a fair number of
automatically-evaluated tests that cover a large swath of the important
functionality implemented, including that tested by the "test"
binaries built by the reference C source, and including comparison
between the KAT output that we produce and that produced by the
reference C implementation. To run the tests and view the results,
execute stack test at a command line.
लोकाः समस्ताः सुखिनोभवंतु
Patches, comments, and discussion are welcome. The most appropriate place for these for the time being is probably the Github repository.