A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9 2026-01-17T16:18:32+00:00 2026-01-17T16:18:32+00:00 jsing 2026-01-17T16:18:32+00:00 urn:sha1:03fc8f9b9ecbb65326348dd8eccc5d22344abefe Make life easier for portable by providing LIBRESSL_USE_.*_ASSEMBLY defines, which enable/disable assembly for a specific algorithm. This means that selected platforms can include the assembly files and specify a define, rather than having to try to patch the crypto_arch.h headers. Discussed with tb@ 2026-01-17T13:55:31+00:00 jsing 2026-01-17T13:55:31+00:00 urn:sha1:1dd1aaafcbe820792a0f2e002a85a22055696509 These have not been used for quite some time. 2025-02-14T12:01:58+00:00 jsing 2025-02-14T12:01:58+00:00 urn:sha1:a89810379a758c9cd27af2462547dc646dcfaa61 Currently, SHA{1,256,512}_ASM defines are used to remove the C implementation of sha{1,256,512}_block_data_order() when it is provided by assembly. However, this prevents the C implementation from being used as a fallback. Rename the C sha*_block_data_order() to sha*_block_generic() and provide a sha*_block_data_order() that calls sha*_block_generic(). Replace the Makefile based SHA*_ASM defines with two HAVE_SHA_* defines that allow these functions to be compiled in or removed, such that machine specific verisons can be provided. This should effectively be a no-op on any platform that defined SHA{1,256,512}_ASM. ok tb@ 2024-08-11T13:02:39+00:00 jsing 2024-08-11T13:02:39+00:00 urn:sha1:5dcef2b3ea9eb7ace8ed74c27534785fc0b87130 Provide a per architecture crypto_arch.h - this will be used in a similar manner to bn_arch.h and will allow for architecture specific #defines and static inline functions. Move the HAVE_AES_* and HAVE_RC4_* defines here. ok tb@ 2024-03-29T11:00:57+00:00 jsing 2024-03-29T11:00:57+00:00 urn:sha1:2f6039e975b851c54c5857fe9253b02da013fb32 Always provide AES_{encrypt,decrypt}() via C functions, which then either use a C implementation or call the assembly implementation. ok tb@ 2024-03-29T07:24:09+00:00 jsing 2024-03-29T07:24:09+00:00 urn:sha1:720ec2c3adcad1ded38a6104e4ca139b4a62ac19 These files are now built on all platforms. 2024-03-29T06:03:21+00:00 jsing 2024-03-29T06:03:21+00:00 urn:sha1:5d94d0325a5b03c1ba85b2e0d51af503a072cc2a This is now built on all platforms. 2024-03-29T04:39:54+00:00 jsing 2024-03-29T04:39:54+00:00 urn:sha1:2c1a87a439933e428607afc0c18d4d12070ae246 Always include aes_core.c and provide AES_set_{encrypt,decrypt}_key() via C functions, which then either use a C implementation or call the assembly implementation. ok tb@ 2024-03-29T02:33:45+00:00 jsing 2024-03-29T02:33:45+00:00 urn:sha1:56504c1b338a0cf1e2340ecd05ecce2ff1b68680 This is now built on all platforms. 2024-03-28T12:52:58+00:00 jsing 2024-03-28T12:52:58+00:00 urn:sha1:c552d9c2f8ca2375f539c9afe37341126127d0f7