cryptoconditions alternatives and similar packages
Based on the "crypto" category.
Alternatively, view cryptoconditions alternatives based on common mentions on social networks and blogs.
-
-
-
-
crypto-api
Haskell generic interface (type classes) for cryptographic algorithms -
-
-
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) -
crypto-pubkey-openssh
OpenSSH keys decoder/encoder -
crypto-enigma
A Haskell Enigma machine simulator with rich display and machine state details. -
crypto-numbers
DEPRECATED - use cryptonite - Cryptographic number related function and algorithms -
-
crypto-random
DEPRECATED - use cryptonite - Cryptographic random class and entropy gatherer with safe API for haskell -
spritz
Implementation of the Spritz RC4-like stream cipher in Haskell -
crypto-classical
A Haskell library for using and attacking Classical Encryption Schemes. -
mcl
Bindings to mcl, a generic and fast pairing-based cryptography library -
crypto-random-effect
haskell library providing a random and securemem effect for extensible effects
Access the most powerful time series database as a service
Do you think we are missing an alternative of cryptoconditions or a related project?
|
Static code analysis for 29 languages.
sponsored
www.sonarqube.org
|
Popular Comparisons
-
cryptoconditionsvscrypto-api
-
cryptoconditionsvsmcl
-
cryptoconditionsvslol
-
cryptoconditionsvsripple
-
cryptoconditionsvspvss
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
Crypto Conditions
Targeting spec: draft-thomas-crypto-conditions-02 of December 20, 2016
Current status
Supports all standard condition types except RSA.
Needs more testing. [Some tests](./test/) exist.
Design
This approach to Crypto Conditions in Haskell has the goals:
- Simple to understand and work with
- Easily extensible
The bottleneck to achieving these goals is extensibility; Haskell does not support dynamic dispatch like OOP languages, and runtime type casting in Haskell is very unnatural and somewhat unsafe.
The solution is to decouple the condition type from the implementation, such that the core algorithms and serialization can work with instances of an "IsCondition" class, and a polymorphic data type can be implemented separately to support the desired condition types and behaviours.
The module [Network.CryptoConditions](./Network/CryptoConditions.hs) supports the standard condition types, library authors wishing to extend CryptoConditions should copy and paste this file into their own project and define their own Condition type.