Dependencies for raaz-0.3.6
Libraries
raaz
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:core
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- vector (>=0.12 && <0.13)
raaz:libverse
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:indef
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:buffer
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:utils
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:mac-indef
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:xchacha-indef
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:digest-api
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:auth-api
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:random-api
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:encrypt-api
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:aead-api
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:implementation
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- raaz
- vector (>=0.12 && <0.13)
raaz:test-core
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- hspec
- HUnit (>=1.2)
- QuickCheck (>=2.4)
- raaz
- vector (>=0.12 && <0.13)
raaz:test-cipher
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- hspec
- HUnit (>=1.2)
- QuickCheck (>=2.4)
- raaz
- vector (>=0.12 && <0.13)
raaz:test-digest
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- hspec
- HUnit (>=1.2)
- QuickCheck (>=2.4)
- raaz
- vector (>=0.12 && <0.13)
raaz:test-auth
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- hspec
- HUnit (>=1.2)
- QuickCheck (>=2.4)
- raaz
- vector (>=0.12 && <0.13)
raaz:test-auth-implementation
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- hspec
- HUnit (>=1.2)
- QuickCheck (>=2.4)
- raaz
- vector (>=0.12 && <0.13)
raaz:bench-types
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- criterion-measurement (>=0.1)
- deepseq (>=1.4 && <1.5)
- pretty
- raaz
- vector (>=0.12 && <0.13)
raaz:bench-prim
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- criterion-measurement (>=0.1)
- deepseq (>=1.4 && <1.5)
- pretty
- raaz
- vector (>=0.12 && <0.13)
raaz:bench-csprg
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- criterion-measurement (>=0.1)
- deepseq (>=1.4 && <1.5)
- pretty
- raaz
- vector (>=0.12 && <0.13)
Executables
raaz
- base (>=4.11 && <4.17)
- bytestring (>=0.10 && <0.12)
- deepseq (>=1.4 && <1.5)
- optparse-applicative (>=0.13.0.0)
- raaz
- vector (>=0.12 && <0.13)
- if impl(ghc<8)
Flags
Manual Flags
Name | Description | Default |
---|---|---|
linux-getrandom | Use the getrandom for system entropy instead of devurandom. Enabled by default but disable this when building for kernel < 3.17. | Enabled |
native | Compile for native architecture. Often this enables a lot of platform specific optimisation which lead to better performance. Do not enable this when packaging though. Also tested only with gcc | Disabled |
wipe-memset | Use plain memset for wiping memory. The problem with its use is that agressive compilers often optimise it out. Raaz uses platform specific functions designed specifically to avoid this and hence enabling this flag is STRONGLY DISCOURAGED. Use it only if your platform does not support such a call. | Disabled |
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info