A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v3.6.2 2022-09-02T13:45:18+00:00 2022-09-02T13:45:18+00:00 tb 2022-09-02T13:45:18+00:00 urn:sha1:c774686171113dd2bff88a75aa40a8d83e3fa99c 2022-09-02T13:38:56+00:00 tb 2022-09-02T13:38:56+00:00 urn:sha1:f0faf4f1dc2213bc86e14491ae6082cdc37e35ec 2022-09-02T11:16:03+00:00 tb 2022-09-02T11:16:03+00:00 urn:sha1:ea362b7ffa5e2058e76c06f429880faef8597010 2022-09-01T14:03:29+00:00 tb 2022-09-01T14:03:29+00:00 urn:sha1:ac27107dc08e1a8f80dc38b5a21afc0c5a04647b 2022-06-28T15:46:07+00:00 bluhm 2022-06-28T15:46:07+00:00 urn:sha1:cf5252db6d33d1bfc3051244edbe04508d96d804 It was incompatible with OpenSSL 3.0. Remove the regression test to check that LibreSSL crypto works with Botan tests. This is better than to keep an outdated Botan in ports. discussed with tb@ beck@ 2022-02-11T16:34:23+00:00 jsing 2022-02-11T16:34:23+00:00 urn:sha1:027a6370238b481d225c2cd67cc22902b173fb6b 2021-12-05T13:01:08+00:00 jsing 2021-12-05T13:01:08+00:00 urn:sha1:7f3ee79566c6df929176e86c34bc32964ed8aaaf This provides test coverage for SCT encoding/decoding. 2020-12-26T00:48:56+00:00 bluhm 2020-12-26T00:48:56+00:00 urn:sha1:80f33da71cc6d1cbd2c0114d03a2d2c25c8d4029 Ensure that it works with obj directory and link regress to build. 2020-09-18T10:19:31+00:00 tb 2020-09-18T10:19:31+00:00 urn:sha1:7e60f46978a7f69c6f9cf1c654e23d1e79621db5 2020-07-23T17:15:35+00:00 schwarze 2020-07-23T17:15:35+00:00 urn:sha1:bc9c51cf66fc92815074622c1c64a0e8bd9d5796 use-after-free and double-free issues in calling programs. The bug was introduced in SSLeay-0.6.0 released on June 21, 1996 and has been present since OpenBSD 2.4. I found the bug while documenting the function. The bug could bite in two ways that looked quite different from the perspective of the calling code: * If a stack was passed in that already contained some X509_INFO objects and an error occurred, all the objects passed in would be freed, but without removing the freed pointers from the stack, so the calling code would probable continue to access the freed pointers and eventually free them a second time. * If the input BIO contained at least two valid PEM objects followed by at least one PEM object causing an error, at least one freed pointer would be put onto the stack, even though the function would return NULL rather than the stack. But the calling code would still have a pointer to the stack, so it would be likely to access the new bogus pointers sooner or later. Fix all this by remembering the size of the input stack on entry and cutting it back to exactly that size when exiting due to an error, but no further. While here, do some related cleanup: * Garbage collect the automatic variables "error" and "i" which were only used at one single place each. * Use NULL rather than 0 for pointers. I like bugfixes that make the code four lines shorter, reduce the number of variables by one, reduce the number of brace-blocks by one, reduce the number if if-statements by one, and reduce the number of else-clauses by one. Tweaks and OK tb@.