openbsd/src/lib/libcrypto/chacha, branch master A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=master 2025-01-25T17:59:44+00:00 Remove #error if OPENSSL_NO_FOO is defined 2025-01-25T17:59:44+00:00 tb 2025-01-25T17:59:44+00:00 urn:sha1:5d52abc236226c5a47c36b07e2256e77141e373a discussed with jsing Revert __bounded__ hack in chacha-merged.c 2024-06-05T19:43:06+00:00 tb 2024-06-05T19:43:06+00:00 urn:sha1:38fd83f2336c4ed37f535189502be491a97ba50a 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 portable 2024-06-01T17:56:44+00:00 tb 2024-06-01T17:56:44+00:00 urn:sha1:476ee576a7f40211b1d3c914b3cb5fedd49177dc Unbreak the namespace build after a broken mk.conf and tool misfire had 2023-07-07T19:37:54+00:00 beck 2023-07-07T19:37:54+00:00 urn:sha1:1ca8095297adf80b48019b5a2d18010ff9e3427f 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 chacha 2023-07-05T16:17:20+00:00 beck 2023-07-05T16:17:20+00:00 urn:sha1:83dc6d5723e9e90220d97b03404c734cc9b8b6ac ok jsing@ Remove UINT32_MAX limitation on ChaCha() and CRYPTO_chacha_20(). 2022-08-20T18:44:58+00:00 jsing 2022-08-20T18:44:58+00:00 urn:sha1:c4f5cc12854a0a64258f9452a1d89656f20a1ca8 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. 2021-10-22T17:43:00+00:00 tb 2021-10-22T17:43:00+00:00 urn:sha1:f88a73e4ec84a81466950e92df5ae0ecab269bde Prompted by a diff by Jonas Termansen. ok jsing add support for xchacha20 and xchacha20-poly1305 2019-01-22T00:59:21+00:00 dlg 2019-01-22T00:59:21+00:00 urn:sha1:4dfb993f9f695f40d03730129e2c082223711b65 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 using 2017-08-13T16:55:31+00:00 jsing 2017-08-13T16:55:31+00:00 urn:sha1:ae4d6b8586e285ed1d7d18a7a183f18f35fc8b1c 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. 2015-12-09T14:07:55+00:00 bcook 2015-12-09T14:07:55+00:00 urn:sha1:9c3c66be91c8f6aee01b5b594cb0340b86a35bfb 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@