A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=tb_20230715 2023-07-15T19:29:46+00:00 2023-07-15T19:29:46+00:00 cvs2svn admin@example.com 2023-07-15T19:29:46+00:00 urn:sha1:72cc860132e5b7971e495ba621dcd0713b5dd801 2023-07-15T19:29:45+00:00 tb 2023-07-15T19:29:45+00:00 urn:sha1:0d87a20f1d7f7c6ae9a6cbb5bc3c2235ee3fe18a 2023-07-15T15:37:05+00:00 jsing 2023-07-15T15:37:05+00:00 urn:sha1:1ccbafc5259d1d9ac7953865285bd87e6824898d MD32_XARRAY was added as a workaround for a broken HP C compiler (circa 1999). Clean it up to simplify the code. No change in generated assembly. 2023-07-15T15:30:43+00:00 jsing 2023-07-15T15:30:43+00:00 urn:sha1:01d9cdcc5f5cbefb02459fe5ffea28c94c1483a3 MD32_XARRAY was added as a workaround for a broken HP C compiler (circa 1999). Clean it up to simplify the code. No change in generated assembly. 2023-07-13T20:59:10+00:00 tb 2023-07-13T20:59:10+00:00 urn:sha1:b47ff84e8ef1dd1e7649dcafb4793c0e190471f7 Oh, joy! The muppets had a feast: they could combine the horrors of EVP with X.509... Return values between -1 and 3 indicating how much work needs to be done, depending on whether methods are present or absent. Needless to say that RSA and EdDSA had inconsistent return values until recently. Instead of interleaving if/else branches, split out two helper functions that do essentially independent things, which results in something that isn't entirely bad. Well, at least not compared to the surrounding code. asn1_item_set_algorithm_identifiers() extracts the signature algorithm from the digest and pkey if known, and sets it on the two X509_ALGOR that may or may not have been passed in. asn1_item_sign() converts data into der and signs. Of course there were also a few leaks and missing error checks. ok jsing 2023-07-12T08:54:18+00:00 tb 2023-07-12T08:54:18+00:00 urn:sha1:efa15ee1c4f122ae67998dd88bdd8ac06e697206 This snuck in with ech_key.c r1.33 because I committed from a dirty tree. 2023-07-12T07:03:24+00:00 tb 2023-07-12T07:03:24+00:00 urn:sha1:ef8535dfb88d26c0fa03b0d83c2108a25692f974 2023-07-11T17:03:44+00:00 tb 2023-07-11T17:03:44+00:00 urn:sha1:5b8e6e5418571fde05d7861d782a926b9a9e8311 2023-07-11T17:02:47+00:00 tb 2023-07-11T17:02:47+00:00 urn:sha1:10a824f0305841181398bf956984e4aabcb42a2d F5 is well-known for needing workaround (go read RFC 8446). In this particular case, it required implementation sending CHs larger than 255 bytes to 0x0300 otherwise their server would hang. This is the same hang that required the CH padding extension which broke other implementations. The CH padding extension was removed ~6 years ago, so hopefully this kludge will no longer needed either. ok jsing 2023-07-11T11:52:35+00:00 tb 2023-07-11T11:52:35+00:00 urn:sha1:dec07df0fa7be98e0b3c49704cb0e6d5e5af1533