A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=master 2026-01-17T14:30:37+00:00 2026-01-17T14:30:37+00:00 jsing 2026-01-17T14:30:37+00:00 urn:sha1:db12bd9b580e2fc1c5c7d3224d2d9d0f534d1b8d Use the same pattern that is now used for most other code - provide HAVE_* defines for functions and use these to selectively enable source code. 2025-12-31T10:16:24+00:00 jsing 2025-12-31T10:16:24+00:00 urn:sha1:126a2d3ddac6e54e807fc6e4f115de54de845ce4 Contrary to naming, the '"June" MMX version' of gcm_ghash_4bit_mmx() uses SSE, while the 'pure-MMX "May" version' does not. This detail got missed when I was untangling OPENSSL_IA32_SSE2. Found the hard way by Tate Baldwin and Dennis Camera. 2025-11-26T10:19:57+00:00 tb 2025-11-26T10:19:57+00:00 urn:sha1:4879f73ba340a5a6a1e4b5812f046c92cf362d95 An upcoming change requires the inclusion of asn1_local.h in x509_local.h which doesn't work due to missing header guards. Add guards to all local headers that don't have them, although reacharounds and multiple inclusions are unlikely to occur for most of those. ok jsing 2025-07-13T06:01:33+00:00 jsing 2025-07-13T06:01:33+00:00 urn:sha1:f0234f5a33ecf3b2784f3e73bdf1e937abe56599 Provide aes_xts_encrypt_internal() and call that from aes_xts_cipher(). Have amd64 and i386 provide their own versions that dispatch to aesni_xts_encrypt()/aesni_xts_decrypt() as appropriate. The AESNI_CAPABLE code and methods can then be removed. ok tb@ 2025-06-28T12:39:10+00:00 jsing 2025-06-28T12:39:10+00:00 urn:sha1:48723f4db60f6f8a8ad8424ffe5e0262d30f397c Provide gcm128_amd64.c and gcm128_i386.c, which contain the appropriate gcm128 initialisation and CPU feature tests for the respective platform. This allows for all of the #define spagetti to be removed from gcm128.c and removes one of the two remaining consumers of crypto_cpu_caps_ia32(). ok tb@ 2025-06-28T12:32:27+00:00 jsing 2025-06-28T12:32:27+00:00 urn:sha1:6021a17fa478e42f9f97414c6114ffe64731e576 Since we always initialise the gmult/ghash function pointers, use the same implementaion of gcm_mul() and gcm_ghash(), regardless of the actual underlying implementation. ok tb@ 2025-06-28T12:25:22+00:00 jsing 2025-06-28T12:25:22+00:00 urn:sha1:426ed7c4756274bd9a701f02587dd1f650775f12 2025-06-09T14:28:34+00:00 jsing 2025-06-09T14:28:34+00:00 urn:sha1:951cd4503ff3c4cc93c1a36cf06138b1ddd739d7 The OPENSSL_IA32_SSE2 flag controls whether a number of the perlasm scripts generate additional implementations that use SSE2 functionality. In all cases except ghash, the code checks OPENSSL_ia32cap_P for SSE2 support, before trying to run SSE2 code. For ghash it generates a CLMUL based implementation in addition to different MMX version (one MMX version hides behind OPENSSL_IA32_SSE2, the other does not), however this does not appear to actually use SSE2. We also disable AES-NI on i386 if OPENSSL_IA32_SSE2. On OpenBSD, we've always defined OPENSSL_IA32_SSE2 so this is effectively a no-op. The only change is that we now check MMX rather than SSE2 for the ghash MMX implementation. ok bcook@ beck@ 2025-06-08T07:49:45+00:00 jsing 2025-06-08T07:49:45+00:00 urn:sha1:b878d30ee2aa2cabb825bb255a5071247dac4893 Fix some things that got missed in the last pass - the majority is use of post-increment rather than unnecessary pre-increment. 2025-06-08T07:38:42+00:00 jsing 2025-06-08T07:38:42+00:00 urn:sha1:7bd57f7872819358d673e776e52068a2886488b6