summaryrefslogtreecommitdiff
path: root/src/lib/libssl/src/crypto/chacha/chacha-merged.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove the libssl/src directorybeck2016-09-031-270/+0
|
* replace u_int8_t with uint8_tbcook2014-07-111-3/+5
| | | | ok beck@
* If a chacha operation does not consume all of the generated key stream,jsing2014-06-241-5/+27
| | | | | | | | | | | | | | | | ensure that we save it and consume it on subsequent writes. Otherwise we end up discarding part of the key stream and instead generate a new block at the start of the next write. This was only an issue for callers that did multiple writes that are not multiples of 64 bytes - in particular, the ChaCha20Poly1305 usage does not hit this problem since it performs encryption in a single-shot. For the same reason, this is also a non-issue when openssl(1) is used to encrypt with ChaCha. Issue identified by insane coder; reported to bugs@ by Joseph M. Schwartz. ok beck@
* Some KNF.jsing2014-06-241-6/+12
|
* tags as requested by miod and teduderaadt2014-06-121-0/+1
|
* KNF.jsing2014-05-151-155/+157
|
* __bounded => __attribute__((__bounded__djm2014-05-101-5/+5
|
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-011-0/+237
ok deraadt@