summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/chacha (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove #error if OPENSSL_NO_FOO is definedtb2025-01-251-5/+1
| | | | discussed with jsing
* Revert __bounded__ hack in chacha-merged.ctb2024-06-051-5/+1
| | | | | Thanks to Viktor Szakats for figuring out that stdint.h was missing in the portable tarballs.
* Neuter the bounded attribute as was done elsewhere for portabletb2024-06-011-1/+5
|
* Unbreak the namespace build after a broken mk.conf and tool misfire hadbeck2023-07-071-1/+2
| | | | | | | | me aliasing symbols not in the headers I was procesing. This unbreaks the namespace build so it will pass again ok tb@
* Hide symbols in chachabeck2023-07-051-1/+6
| | | | ok jsing@
* Remove UINT32_MAX limitation on ChaCha() and CRYPTO_chacha_20().jsing2022-08-201-3/+23
| | | | | | | | We can avoid this unnecessary limitation by calling chacha_encrypt_bytes() multiple times internally. In the case of ChaCha(), the caller still needs to ensure that the same IV is not used for more than 2^70 bytes. ok tb@
* Switch from u_int and u_char to u32 and u8 to avoid portability issues.tb2021-10-221-17/+14
| | | | | | Prompted by a diff by Jonas Termansen. ok jsing
* add support for xchacha20 and xchacha20-poly1305dlg2019-01-223-3/+63
| | | | | | | xchacha is a chacha stream that allows for an extended nonce, which in turn makes it feasible to use random nonces. ok tb@
* Convert the sigma and tau initialisers to byte arrays, rather than usingjsing2017-08-131-3/+12
| | | | | | | | | strings. The original code is perfectly valid C, however it causes some compilers to complain since it lacks room for a string NUL terminator and the compiler is not smart enough to realise that these are only used as byte arrays and never treated as strings. ok bcook@ beck@ inoguchi@
* Change the counter argument for CRYPTO_chacha_20 to be 64-bits on all platforms.bcook2015-12-092-5/+6
| | | | | | | | | | | The recently-added EVP_aead_chacha20_poly1305_ietf() function, which implements informational RFC 7539, "ChaCha20 and Poly1305 for IETF Protocols", needs a 64-bit counter to avoid truncation on 32-bit platforms. The existing TLS ChaCha20-Poly1305 ciphersuite is not impacted by this, but making this change requires an ABI bump. ok jsing@, "Looks sane" beck@
* Add missing year to copyright.jsing2014-07-251-2/+2
|
* replace u_int8_t with uint8_tbcook2014-07-111-3/+5
| | | | ok beck@
* add missing stdint. include for uint32_t, etc.bcook2014-07-081-1/+4
| | | | ok beck@ jsing@
* If a chacha operation does not consume all of the generated key stream,jsing2014-06-243-7/+46
| | | | | | | | | | | | | | | | 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-123-0/+3
|
* Get the public headers from the official place with <openssl/ >deraadt2014-05-311-1/+1
| | | | from Brent Cook
* KNF.jsing2014-05-152-156/+158
|
* __bounded => __attribute__((__bounded__djm2014-05-101-5/+5
|
* Provide an EVP implementation for ChaCha.jsing2014-05-012-0/+31
| | | | ok miod@
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-013-0/+314
ok deraadt@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-17 08:50:13 +0000