haskell/cryptonite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
610 Commits 15 Branches 30 Tags 2.5 MiB
C 51.5%
Haskell 48.3%
Shell 0.2%
a8c80e9531
Go to file
Luke Taylor a8c80e9531 Add a check for salt length in bcrypt function 
Raises an error (as the original doc claimed) if the salt is not the
required length of 16 bytes.

validatePasswordEither doesn't require separate checking since the hash
length as a whole is checked, implicitly ensuring the salt is the right
length. Therefore it shouldn't be possible to trigger the error by
calling this function.

Fixes #93.
2016-08-22 13:41:42 +02:00
benchs [bench] add some number for chacha poly1305 2015-07-30 14:40:54 +01:00
cbits rdrand-related code and build flag changes 2016-08-22 13:34:38 +02:00
Crypto Add a check for salt length in bcrypt function 2016-08-22 13:41:42 +02:00
gen Improve context memory usage of Keccak and SHA3 2016-03-26 10:29:33 +00:00
tests Add a check for salt length in bcrypt function 2016-08-22 13:41:42 +02:00
.gitignore [bench] ignore binaries 2015-05-02 05:43:06 +01:00
.travis.yml update .travis 2016-01-14 19:17:43 +00:00
CHANGELOG.md Fix serialization of ECDH and DH 2016-04-09 17:13:51 +01:00
cryptonite.cabal rdrand-related code and build flag changes 2016-08-22 13:34:38 +02:00
cryptonite.sublime-project wip 2015-04-08 14:12:58 +01:00
LICENSE update main license 2015-03-12 05:44:23 +00:00
Makefile add dummy makefile to run QA 2015-05-03 14:26:21 +01:00
QA.hs [QA] update to latest state of things 2015-07-29 10:02:44 +01:00
README.md add BSD to support list 2015-07-08 13:46:42 +02:00
Setup.hs initial commit. 2014-07-04 14:58:01 +01:00

README.md

cryptonite

Join the chat at https://gitter.im/vincenthz/cryptonite Build Status BSD Haskell

Cryptonite is a haskell repository of cryptographic primitives. Each crypto algorithm have specificities, that are hard to wrap in common APIs and types, so instead of trying to provide a common ground for algorithms that wouldn't allow to provide all different usage or a really complicated system, this just provide a non-consistant low-level API.

If you have no idea what're you doing, please do not use this directly, rely on higher level protocols or higher level implementation.

Documentation: cryptonite on hackage

Versioning

Development versions are an incremental number prefixed by 0. No specific meaning is associated with the versions, specially no API stability.

Production versions : TBD

Coding Style

The coding style of this project mostly follows: haskell-style

Support

cryptonite supports the following platform:

  • Windows >= 8
  • OSX >= 10.8
  • Linux
  • BSDs

On the following architectures:

  • x86-64
  • i386

On the following haskell versions:

  • GHC 7.0.x
  • GHC 7.4.x
  • GHC 7.6.x
  • GHC 7.8.x
  • GHC 7.10.x

Further platforms and architectures probably works too, but until maintainer(s) don't have regular access to them, we can't commit for further support

Known Building Issues

on OSX <= 10.7, the system compiler doesn't understand the '-maes' option, and with the lack of autodetection feature builtin in .cabal file, it is left on the user to disable the aesni. See the [Disabling AESNI] section

Disabling AESNI

It may be useful to disable AESNI (for building, testing or runtime purpose), and one can do that with the support_aesni flag.

As part of configure of cryptonite:

  cabal configure --flag='-support_aesni'

or as part of an installation:

  cabal install --constraint="cryptonite -support_aesni"

For help with cabal flags, see: stackoverflow : is there a way to define flags for cabal

Links

TODO

  • add support for XSalsa