Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Update BoringSSL | Benjamin Barenblat | 2018-12-21 |
| | |||
* | Update BoringSSL | Benjamin Barenblat | 2018-09-19 |
| | |||
* | Update BoringSSL | Benjamin Barenblat | 2018-07-03 |
| | | | | | | | https://boringssl.googlesource.com/boringssl/+/03de6813d8992a649092b4874ef0ebc022e2f58a means BoringSSL now by default includes relocations that don't play well with shared libraries. Make `cabal build --enable-shared` work again by building all BoringSSL code as PIC. | ||
* | Update BoringSSL | Benjamin Barenblat | 2018-03-23 |
| | |||
* | Update BoringSSL | Benjamin Barenblat | 2018-01-24 |
| | |||
* | Begin writing btls, a Haskell crypto and TLS library using BoringSSL | Benjamin Barenblat | 2017-12-30 |
So far, btls provides SHA-224, SHA-256, SHA-384, and SHA-512 algorithms. To do that, I - vendor BoringSSL and create a custom `Setup.hs` to build it, - wrap a number of functions and values from BoringSSL's EVP subsystem, and - implement the four SHA-2 algorithms using the wrapped routines. I provide conformance tests incorporating the official NIST example vectors and the vectors used in the Go SHA-2 test suite. The tests also use SmallCheck to compare btls’s SHA-2 implementations with those provided by the system’s Coreutils and openssl(1) installations. |