<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib/libcrypto/err, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib/libcrypto/err?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib/libcrypto/err?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2019-10-17T14:28:53Z</updated>
<entry>
<title>Provide err_clear_last_constant_time() as a way of clearing an error from</title>
<updated>2019-10-17T14:28:53Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-10-17T14:28:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b96c5e8cba0627f151d59c00df351151cce50674'/>
<id>urn:sha1:b96c5e8cba0627f151d59c00df351151cce50674</id>
<content type='text'>
the top of the error stack in constant time.

This will be used by upcoming RSA changes.

From OpenSSL 1.1.1d.

ok inoguchi@ tb@
</content>
</entry>
<entry>
<title>Load CMS error strings.</title>
<updated>2019-09-09T17:56:21Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-09-09T17:56:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=71f14ff6624461261a8cd75e9d6e89aeab2f0086'/>
<id>urn:sha1:71f14ff6624461261a8cd75e9d6e89aeab2f0086</id>
<content type='text'>
</content>
</entry>
<entry>
<title>KNF: move two opening curly braces of function bodies to their own lines</title>
<updated>2018-04-03T21:59:37Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2018-04-03T21:59:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d595aa6150169974b48e4afe6b0a5ce9496e1259'/>
<id>urn:sha1:d595aa6150169974b48e4afe6b0a5ce9496e1259</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bring in compatibility for OpenSSL 1.1 style init functions.</title>
<updated>2018-03-17T16:20:01Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2018-03-17T16:20:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e68eaf899d992866359733a944d0495c6196ce94'/>
<id>urn:sha1:e68eaf899d992866359733a944d0495c6196ce94</id>
<content type='text'>
This adds OPENSSL_init_crypto and OPENSSL_init_ssl, as well
thread safety modifications for the existing LibreSSL init
functions.  The initialization routines are called automatically
by the normal entry points into the library, as in newer OpenSSL

ok jsing@, nits by tb@ and deraadt@
</content>
</entry>
<entry>
<title>Mark ERR_add_error_data and ERR_add_error_vdata as not for internal use,</title>
<updated>2017-02-20T23:21:19Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2017-02-20T23:21:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3a78e2ddba7fed4643dc23ea4e47269d2607db51'/>
<id>urn:sha1:3a78e2ddba7fed4643dc23ea4e47269d2607db51</id>
<content type='text'>
and document ERR_asprintf_error_data as their replacement.
ok jsing@, ingo@
</content>
</entry>
<entry>
<title>Revert previous; the implementation is incorrect since it assumes that the</title>
<updated>2017-02-07T15:52:33Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2017-02-07T15:52:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d2cab73aa41b4e1e839a8436bfd0fa46b20e2826'/>
<id>urn:sha1:d2cab73aa41b4e1e839a8436bfd0fa46b20e2826</id>
<content type='text'>
provided error code matches the error that is currently on the top of the
error stack.
</content>
</entry>
<entry>
<title>Add file and line to the LibreSSL error strings sine we are no longer in</title>
<updated>2017-02-07T03:11:11Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2017-02-07T03:11:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=85912072637bb2017d1e402c3c585d326eb0872c'/>
<id>urn:sha1:85912072637bb2017d1e402c3c585d326eb0872c</id>
<content type='text'>
1989, VMS, or MS/DOS and we all run Brobdingnagian C compilers that have
can now be counted on to achieve this level of sophistication nearly
everywhere.
ok jsing@
</content>
</entry>
<entry>
<title>Send the function codes from the error functions to the bit bucket,</title>
<updated>2017-01-29T17:49:22Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2017-01-29T17:49:22Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5067ae9f807f8af9e6350e51e6a54619386c06ba'/>
<id>urn:sha1:5067ae9f807f8af9e6350e51e6a54619386c06ba</id>
<content type='text'>
as was done earlier in libssl. Thanks inoguchi@ for noticing
libssl had more reacharounds into this.
ok jsing@ inoguchi@
</content>
</entry>
<entry>
<title>Hide SSLerr() under #ifndef LIBRESSL_INTERNAL since we shouldn't be</title>
<updated>2017-01-26T12:07:06Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2017-01-26T12:07:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1de91d6b8b17a2c5804a28b7f87b9035fb3cb94f'/>
<id>urn:sha1:1de91d6b8b17a2c5804a28b7f87b9035fb3cb94f</id>
<content type='text'>
using it anymore
ok jsing@
</content>
</entry>
<entry>
<title>unifdef OPENSSL_NO_CMS</title>
<updated>2016-10-19T16:49:11Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2016-10-19T16:49:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ec0579e6b1953489518d18b16f6865d409983be3'/>
<id>urn:sha1:ec0579e6b1953489518d18b16f6865d409983be3</id>
<content type='text'>
</content>
</entry>
</feed>
