<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/etc/rc, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/etc/rc?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/etc/rc?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-01-24T06:17:37Z</updated>
<entry>
<title>retire rebound etc bits to the attic</title>
<updated>2020-01-24T06:17:37Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2020-01-24T06:17:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=166e2b0880481affc6acc9fff955b96cdfa785d6'/>
<id>urn:sha1:166e2b0880481affc6acc9fff955b96cdfa785d6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>move /usr and var remounting (nfs diskless case...) earlier, so that</title>
<updated>2019-11-11T04:55:37Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-11-11T04:55:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=db15c4eb4a1deef345cefe193839fffbde18c954'/>
<id>urn:sha1:db15c4eb4a1deef345cefe193839fffbde18c954</id>
<content type='text'>
unwind can be started (silently) before pf is configured (for those
few weirdos who use hostnames in pf.conf...).  Other unidentified concerns
may be improved by this startup re-ordering, so let's give it a try.
discussed with florian.
</content>
</entry>
<entry>
<title>use $(&lt;file) instead of $(cat file) since this script uses ksh; ok ajacoutot@</title>
<updated>2019-11-10T15:02:36Z</updated>
<author>
<name>naddy</name>
<email>naddy@openbsd.org</email>
</author>
<published>2019-11-10T15:02:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=287d24a6afa61cb03f4fde5977ca523f737241d7'/>
<id>urn:sha1:287d24a6afa61cb03f4fde5977ca523f737241d7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>we have emergency entropy injection code in rc, for if the bootblocks and</title>
<updated>2019-11-06T16:26:24Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-11-06T16:26:24Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6d6858e649b481d11efc65c60bf7b3faf31132da'/>
<id>urn:sha1:6d6858e649b481d11efc65c60bf7b3faf31132da</id>
<content type='text'>
other methods failed to inject/churn the rng enough.  Move it up far earlier.
ok naddy sthen kettenis
</content>
</entry>
<entry>
<title>for now, only mix in sysctl hw.{uuid,serialno,sensors} to /dev/random.</title>
<updated>2019-10-06T16:16:19Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2019-10-06T16:16:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e0e8f599fc9f78ad752ce6827bdfbb5bf60da229'/>
<id>urn:sha1:e0e8f599fc9f78ad752ce6827bdfbb5bf60da229</id>
<content type='text'>
as found the hard way by d.rauschenb@gmail on an old fujitsu siemens
machine, reading all of hw (notable hw.setperf) can have unexpected
side-effects.  ok deraadt
</content>
</entry>
<entry>
<title>feed "sysctl hw" into /dev/random; a cheap way to feed in sensor data</title>
<updated>2019-10-02T17:15:40Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2019-10-02T17:15:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1c7698b38d6f94c2b3c20368d3cf7f428deeaa04'/>
<id>urn:sha1:1c7698b38d6f94c2b3c20368d3cf7f428deeaa04</id>
<content type='text'>
as a one-shot at boot without more complex kernel work, and also includes
some serial numbers/guids which may add a little more entropy e.g. for
systems where /etc/random.seed may be known (e.g. cloned disk images).
"why not" deraadt@
</content>
</entry>
<entry>
<title>ld.so boot cleanup support:</title>
<updated>2019-05-10T13:29:21Z</updated>
<author>
<name>guenther</name>
<email>guenther@openbsd.org</email>
</author>
<published>2019-05-10T13:29:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c0197e40dd4094880fe205f9c12d3e12e14e7ff3'/>
<id>urn:sha1:c0197e40dd4094880fe205f9c12d3e12e14e7ff3</id>
<content type='text'>
 - put functions and data which are only used before calling the executable's
   start function into their own page-aligned segments for unmapping
   (only done on amd64, arm64, armv7, powerpc, and sparc64 so far)
 - pass .init_array and .preinit_array functions an addition argument which
   is a callback to get a structure which includes a function that frees
   the boot text and data
 - sometimes delay doing RELRO processing: for a shared-object marked
   DF_1_INITFIRST do it after the object's .init_array, for the executable
   do it after the .preinit_array
 - improve test-ld.so to link against libpthread and trigger its initialization
   late
libc changes to use this will come later

ok kettenis@
</content>
</entry>
<entry>
<title>revert previous. ifconfig errors may be interesting... to be revisited.</title>
<updated>2019-04-01T11:39:46Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2019-04-01T11:39:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3667ef4e333d46380e4a11cafbb26052adee5382'/>
<id>urn:sha1:3667ef4e333d46380e4a11cafbb26052adee5382</id>
<content type='text'>
</content>
</entry>
<entry>
<title>catch/hide errors from ifconfig carp in case there is no carp.</title>
<updated>2019-04-01T06:59:36Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2019-04-01T06:59:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3b14d2e9efa42ab6d3c90efd75cae750b845f594'/>
<id>urn:sha1:3b14d2e9efa42ab6d3c90efd75cae750b845f594</id>
<content type='text'>
ok deraadt
</content>
</entry>
<entry>
<title>Remove -S from install commands</title>
<updated>2019-02-24T12:57:13Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2019-02-24T12:57:13Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d125f36660e746ef78f30e303c3b69861c0c6aaa'/>
<id>urn:sha1:d125f36660e746ef78f30e303c3b69861c0c6aaa</id>
<content type='text'>
As of usr.bin/xinstall/install.c revision 1.68, -S is a no-op and
install(1) will always create files safely, thus clean the option usage
from the tree.

Diff from Lauri Tirkkonen &lt;lotheac at iki dot fi&gt;, thanks.
</content>
</entry>
</feed>
