<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/lib, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/lib?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/lib?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-06-10T20:19:29Z</updated>
<entry>
<title>Provide an optimized implementation of ffs(3) in the kernel on</title>
<updated>2020-06-10T20:19:29Z</updated>
<author>
<name>naddy</name>
<email>naddy@openbsd.org</email>
</author>
<published>2020-06-10T20:19:29Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d41240fab998b3c42f736af0544339ebedba7e73'/>
<id>urn:sha1:d41240fab998b3c42f736af0544339ebedba7e73</id>
<content type='text'>
arm64/powerpc/powerpc64, making use of the count leading zeros
instruction.

powerpc testing by cwen@; ok kettenis@ deraadt@
</content>
</entry>
<entry>
<title>If we pass a packet length larger than 2^16, we should panic() instead</title>
<updated>2020-05-19T12:54:37Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2020-05-19T12:54:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=396ee6d6b62cd4725fd412b6e857e55aee684d35'/>
<id>urn:sha1:396ee6d6b62cd4725fd412b6e857e55aee684d35</id>
<content type='text'>
of returning -1.  With a return type of u_int16_t, -1 is not different
to a valid checksum.  For incoming packets, the header lengths don't
exceed that size anyway, but for outgoing packets it's better to see
if our bootloader crafts a broken one.

Discussed with gerhard@
ok deraadt@ procter@
</content>
</entry>
<entry>
<title>Sync in_cksum.c to the same version ospfd has.  This fixes problems</title>
<updated>2020-05-18T17:01:02Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2020-05-18T17:01:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=419596d7e7d9396d7ff0a802278e9a2db9b17f1e'/>
<id>urn:sha1:419596d7e7d9396d7ff0a802278e9a2db9b17f1e</id>
<content type='text'>
with odd packet lengths, which can happen when using TFTP to load
a file with an odd length.  ospfd actually took dvmrpd's version
in 2006 to fix the same issue, and both daemons implementations are
the same.  For the bootloader we keep the consts from the previous
version and replace the fatal with a print and return.

ok deraadt@
</content>
</entry>
<entry>
<title>Add __lshrti3 to libkern and use it on sparc64</title>
<updated>2020-04-02T01:01:13Z</updated>
<author>
<name>jca</name>
<email>jca@openbsd.org</email>
</author>
<published>2020-04-02T01:01:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cb5d789f0ad63660290375fc11743b019f6a773d'/>
<id>urn:sha1:cb5d789f0ad63660290375fc11743b019f6a773d</id>
<content type='text'>
With this it's possible to build the kernel using clang.
Discussed with claudio@, ok deraadt@
</content>
</entry>
<entry>
<title>Next step in prepping for ffs2 installs: introduce a new install script var</title>
<updated>2020-02-29T07:31:34Z</updated>
<author>
<name>otto</name>
<email>otto@openbsd.org</email>
</author>
<published>2020-02-29T07:31:34Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6221c7eaa9bd32362d70d40c1870fbf4a4bf81cf'/>
<id>urn:sha1:6221c7eaa9bd32362d70d40c1870fbf4a4bf81cf</id>
<content type='text'>
MDFSOPT and add a missing prototype.
</content>
</entry>
<entry>
<title>Remove non-__STDC__ assert macros from &lt;lib/libkern/libkern.h&gt;.</title>
<updated>2020-02-26T14:23:15Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2020-02-26T14:23:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e1bcc96db2d520dc36554d8fc038526d129fdc07'/>
<id>urn:sha1:e1bcc96db2d520dc36554d8fc038526d129fdc07</id>
<content type='text'>
The macros are defined in a part of the header where a C compiler
is required. In addition, the macros expand to C code, so it looks
unnecessary to define the asserts with traditional cpp in mind.

OK cheloha@, mpi@
</content>
</entry>
<entry>
<title>Add an element to the marks array to store the virtual address of the</title>
<updated>2019-11-29T20:53:13Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2019-11-29T20:53:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=934484026c7a2904fb164ecd78330ff78899d549'/>
<id>urn:sha1:934484026c7a2904fb164ecd78330ff78899d549</id>
<content type='text'>
entry point.

ok mlarkin@, deraadt@
</content>
</entry>
<entry>
<title>Implement a hexdump command in the boot loader.  This helps to</title>
<updated>2019-11-28T00:17:10Z</updated>
<author>
<name>bluhm</name>
<email>bluhm@openbsd.org</email>
</author>
<published>2019-11-28T00:17:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3fbdbb315f0b99e633dc16e3d2b7a673b2569d3d'/>
<id>urn:sha1:3fbdbb315f0b99e633dc16e3d2b7a673b2569d3d</id>
<content type='text'>
inspect the memory layout that the firmware has created.  It is
especially useful for UEFI debugging.
OK deraadt@ kettenis@
</content>
</entry>
<entry>
<title>Give some END()s to assembly symbols.</title>
<updated>2019-11-05T08:16:43Z</updated>
<author>
<name>mpi</name>
<email>mpi@openbsd.org</email>
</author>
<published>2019-11-05T08:16:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6abd9ea796a8bef365c616b03174fbc2051daf73'/>
<id>urn:sha1:6abd9ea796a8bef365c616b03174fbc2051daf73</id>
<content type='text'>
ok kettenis@, jca@
</content>
</entry>
<entry>
<title>Reduce BOOTRANDOM_MAX to 256.  naddy pointed out there's no point having</title>
<updated>2019-11-01T20:54:52Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-11-01T20:54:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=b4bcf6304410501bfbe0df1a65ef5b432faa8426'/>
<id>urn:sha1:b4bcf6304410501bfbe0df1a65ef5b432faa8426</id>
<content type='text'>
it larger than RC4STATE.  A long discussion ensued. In conclusion all
entropy inputs are either satisfactory enough, or just as shitty at 512.
</content>
</entry>
</feed>
