openbsd/src/lib/libcrypto/md5, branch libressl-v4.1.2A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=libressl-v4.1.22025-01-25T17:59:44+00:00Remove #error if OPENSSL_NO_FOO is defined2025-01-25T17:59:44+00:00tb2025-01-25T17:59:44+00:00urn:sha1:5d52abc236226c5a47c36b07e2256e77141e373a
discussed with jsing
Remove now unused perlasm script for MD5 on amd64.2025-01-24T13:38:28+00:00jsing2025-01-24T13:38:28+00:00urn:sha1:980bb6f6f24a7e2c0b47ad6bb0100e661d5d0027Provide a readable assembly implementation for MD5 on amd64.2025-01-24T13:35:04+00:00jsing2025-01-24T13:35:04+00:00urn:sha1:e645f65a85d604ca35a8889b91950b72ea837f74
This appears to be about 5% faster than the current perlasm version on a
modern Intel CPU.
While here rename md5_block_asm_data_order to md5_block_data_order, for
consistency with other hashes.
ok tb@
Improve bit counter handling in MD5.2025-01-19T07:51:41+00:00jsing2025-01-19T07:51:41+00:00urn:sha1:de01c8928427154fc6038fb682dd8521cd3805d5
Like most hashes, MD5 needs to keep count of the number of bits in the
message being processed. However, rather than using a 64 bit counter this
is implemented using two 32 bit values (which is exposed in the public
API). Even with this hurdle, we can still use 64 bit math and let the
compiler figure out how to best handle the situation (hopefully avoiding
compiler warnings on 16 bit platforms in the process!). On amd64 this code
now requires two instructions, instead of the previous five.
While here remove a comment that is excessively visible and no longer
completely accurate (and if you're going to redefine types like MD5_WORD
you kinda need to know what you're doing).
ok tb@ (who's going to miss the dear diary style comments)
Reverse order of attributes2024-06-01T07:44:11+00:00tb2024-06-01T07:44:11+00:00urn:sha1:2d4c4d8a62665e7e18f808fffc2503822482f6d7
requested by jsing on review
Remove support for static buffers in HMAC/digests2024-06-01T07:36:17+00:00tb2024-06-01T07:36:17+00:00urn:sha1:0cd26255605cab2a8643bb8585c4148069240e3c
HMAC() and the one-step digests used to support passing a NULL buffer and
would return the digest in a static buffer. This design is firmly from the
nineties, not thread safe and it saves callers a single line. The few ports
that used to rely this were fixed with patches sent to non-hostile (and
non-dead) upstreams. It's early enough in the release cycle that remaining
uses hidden from the compiler should be caught, at least the ones that
matter.
There won't be that many since BoringSSL removed this feature in 2017.
https://boringssl-review.googlesource.com/14528
Add non-null attributes to the headers and add a few missing bounded
attributes.
ok beck jsing
Load in the top of the loop, as we do for other hash implementations.2024-03-28T08:00:08+00:00jsing2024-03-28T08:00:08+00:00urn:sha1:1c0c0921adbf436279c7a07d6495428a26e7f71eStop including md32_common.h in md5.c and remove unused defines.2024-03-26T05:55:15+00:00jsing2024-03-26T05:55:15+00:00urn:sha1:552d4614f7d70b3a4f09def8dc1c5fb051682d47
This is now no longer needed.
ok tb@
Include stdint.h for uintptr_t.2024-03-26T05:46:13+00:00jsing2024-03-26T05:46:13+00:00urn:sha1:e340b8decae9fd52f83119ce0ffbdf7b04b53d8dDemacro MD5 and improve data loading.2024-03-26T05:21:35+00:00jsing2024-03-26T05:21:35+00:00urn:sha1:60ada654237dd4cad2245c11f7a9ecf4f6091bc5
Use static inline functions instead of macros and improve handling of
aligned data. Also number rounds as per RFC 1321.
ok tb@