<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-06-22T13:42:06Z</updated>
<entry>
<title>spelling fix;</title>
<updated>2020-06-22T13:42:06Z</updated>
<author>
<name>jmc</name>
<email>jmc@openbsd.org</email>
</author>
<published>2020-06-22T13:42:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bc0ee81f054f4f7d750f13eea3b7e67fa5aac56c'/>
<id>urn:sha1:bc0ee81f054f4f7d750f13eea3b7e67fa5aac56c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Extend kqueue interface with EVFILT_EXCEPT filter.</title>
<updated>2020-06-22T13:14:32Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2020-06-22T13:14:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=7ab02df9ba969938f0d288bc81680642c429c9c4'/>
<id>urn:sha1:7ab02df9ba969938f0d288bc81680642c429c9c4</id>
<content type='text'>
This filter, already implemented in macOS and Dragonfly BSD, returns
exceptional conditions like the reception of out-of-band data.

The functionnality is similar to poll(2)'s POLLPRI &amp; POLLRDBAND and
it can be used by the kqfilter-based poll &amp; select implementation.

ok millert@ on a previous version, ok visa@
</content>
</entry>
<entry>
<title>basic macro cleanup: .Fo for long .Fn lines, .Fa for struct fields,</title>
<updated>2020-06-20T09:26:54Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-20T09:26:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c4b445c6ea7c933c23ce409203a3ab016114031b'/>
<id>urn:sha1:c4b445c6ea7c933c23ce409203a3ab016114031b</id>
<content type='text'>
avoid \*(Gt and \*(Lt, .Dv NULL, .Cm for pledge promises
</content>
</entry>
<entry>
<title>add missing ENVIRONMENT. HISTORY, and AUTHORS sections,</title>
<updated>2020-06-20T08:41:37Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-20T08:41:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=64aa3d5ef4a6ded9eda42a773eef7bf65cfb8cbb'/>
<id>urn:sha1:64aa3d5ef4a6ded9eda42a773eef7bf65cfb8cbb</id>
<content type='text'>
and a few other wording and markup improvements while here;
OK jmc@ ratchov@
</content>
</entry>
<entry>
<title>We inherited the constant time CBC padding removal from BoringSSL, but</title>
<updated>2020-06-19T21:26:40Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2020-06-19T21:26:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=47f04e975a4b111b62acf5a62c889efa5182d30a'/>
<id>urn:sha1:47f04e975a4b111b62acf5a62c889efa5182d30a</id>
<content type='text'>
missed a subsequent fix for an off-by-one in that code.  If the first
byte of a CBC padding of length 255 is mangled, we don't detect that.

Adam Langley's BoringSSL commit 80842bdb44855dd7f1dde64a3fa9f4e782310fc7

Fixes the failing tlsfuzzer lucky 13 test case.

ok beck inoguchi
</content>
</entry>
<entry>
<title>mark the functions documented in des_read_pw(3) as deprecated</title>
<updated>2020-06-19T17:17:13Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-19T17:17:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=0ff6b527cb823323f4cf21fd5216a4546f65d996'/>
<id>urn:sha1:0ff6b527cb823323f4cf21fd5216a4546f65d996</id>
<content type='text'>
and point to UI_UTIL_read_pw(3) instead;
tb@ agrees with the general direction
</content>
</entry>
<entry>
<title>document X509_get0_pubkey_bitstr(3),</title>
<updated>2020-06-19T14:31:29Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-19T14:31:29Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ee8bd9906a80518fcee49b60ce23d7ac246eba65'/>
<id>urn:sha1:ee8bd9906a80518fcee49b60ce23d7ac246eba65</id>
<content type='text'>
correct the description of X509_get_X509_PUBKEY(3),
document error handling of the read accessors,
and mention the relevant STANDARDS
</content>
</entry>
<entry>
<title>document error handling of X509_PUBKEY_get0(3) and X509_PUBKEY_get(3)</title>
<updated>2020-06-19T14:04:25Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-19T14:04:25Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bdc03493e19055eb260a58abac8f2df1c6b8d6c9'/>
<id>urn:sha1:bdc03493e19055eb260a58abac8f2df1c6b8d6c9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge documentation of X509_get0_serialNumber(3) from OpenSSL-1.1.1</title>
<updated>2020-06-19T12:01:20Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-19T12:01:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a560d792221a6c37cb62df1531e3684d468cd8f3'/>
<id>urn:sha1:a560d792221a6c37cb62df1531e3684d468cd8f3</id>
<content type='text'>
which is still under a free license.  Wording tweaked by me.
</content>
</entry>
<entry>
<title>uint8_t is a discrete, not a continuous type,</title>
<updated>2020-06-18T16:21:28Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-18T16:21:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e04d4d7c1e35b856678b6845fd91bb246c1c0a0c'/>
<id>urn:sha1:e04d4d7c1e35b856678b6845fd91bb246c1c0a0c</id>
<content type='text'>
and some other wording improvements with respect to types;
OK ratchov@
</content>
</entry>
</feed>
