<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sbin/pfctl/pfctl.c, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sbin/pfctl/pfctl.c?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sbin/pfctl/pfctl.c?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-01-16T01:02:20Z</updated>
<entry>
<title>Fail on missing anchor</title>
<updated>2020-01-16T01:02:20Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2020-01-16T01:02:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ad846651a1e57f4044de08e014c62f6c17306af2'/>
<id>urn:sha1:ad846651a1e57f4044de08e014c62f6c17306af2</id>
<content type='text'>
There is no reason to continue on anchor specific paths if the given
anchor does not exist.

OK sashan
</content>
</entry>
<entry>
<title>Do the actual pfr_strerror() to pf_strerror() rename</title>
<updated>2020-01-15T22:38:30Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2020-01-15T22:38:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c802a0d9d6a6510e658984688f179f6777ccfce2'/>
<id>urn:sha1:c802a0d9d6a6510e658984688f179f6777ccfce2</id>
<content type='text'>
Missed in previous
</content>
</entry>
<entry>
<title>Unify error message for nonexisting anchors</title>
<updated>2020-01-15T22:31:51Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2020-01-15T22:31:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e5c920154c2024677fa8b335bbe529eaa6a4e705'/>
<id>urn:sha1:e5c920154c2024677fa8b335bbe529eaa6a4e705</id>
<content type='text'>
pf(4) returns EINVAL for DIOCGETRULE, DIOCGETRULES and DIOCGETRULESET if
the specified anchor does not exist.

Extend and rename {pfr -&gt; pf}_strerror() to make error message more
consistent.

There are other occasions as well but those need additional tweaks;
that's stuff for another diff.

OK and rename from sashan
</content>
</entry>
<entry>
<title>Print the main ruleset/anchor as "/" not "&lt;root&gt;" for consistency</title>
<updated>2020-01-15T13:42:39Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2020-01-15T13:42:39Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=baa66dbe09e9b06485965f736a81919fb26ad31d'/>
<id>urn:sha1:baa66dbe09e9b06485965f736a81919fb26ad31d</id>
<content type='text'>
OK sashan
</content>
</entry>
<entry>
<title>Enable pfctl(8) to recursively flush rules and tables from PF driver.  The</title>
<updated>2020-01-15T11:52:50Z</updated>
<author>
<name>sashan</name>
<email>sashan@openbsd.org</email>
</author>
<published>2020-01-15T11:52:50Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ae711728d410d2bb41f3a563f2e2ebdede715edc'/>
<id>urn:sha1:ae711728d410d2bb41f3a563f2e2ebdede715edc</id>
<content type='text'>
recursive operation ("pfctl -a '*' ...") works for '-s' option already. This
change enables the same thing for '-F' option, so "pfctl -a '*' -Fa" will flush
everything from PF driver.

The idea was discussed with many on tech@ in spring 2019.

OK kn@
</content>
</entry>
<entry>
<title>Fix function name in error message (zap trailing s)</title>
<updated>2019-11-27T19:42:56Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2019-11-27T19:42:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5b2c7c22150964b4b864e3be9d79b5cb74f65287'/>
<id>urn:sha1:5b2c7c22150964b4b864e3be9d79b5cb74f65287</id>
<content type='text'>
</content>
</entry>
<entry>
<title>pfctl_reset() must set syncookies settings back to default</title>
<updated>2019-08-15T18:44:53Z</updated>
<author>
<name>sashan</name>
<email>sashan@openbsd.org</email>
</author>
<published>2019-08-15T18:44:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bb94865e4f07e87e026b323657b354836e8082ba'/>
<id>urn:sha1:bb94865e4f07e87e026b323657b354836e8082ba</id>
<content type='text'>
(bug found and fix tested by Jesper Wallin)

OK deraadt OK kn
</content>
</entry>
<entry>
<title>Add parentheses for readability</title>
<updated>2019-07-09T16:42:48Z</updated>
<author>
<name>kn</name>
<email>kn@openbsd.org</email>
</author>
<published>2019-07-09T16:42:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ff93619fa5f16c5e110ab1ba8ff15eb7f10bbf0b'/>
<id>urn:sha1:ff93619fa5f16c5e110ab1ba8ff15eb7f10bbf0b</id>
<content type='text'>
Prompted by and OK deraadt
</content>
</entry>
<entry>
<title>When system calls indicate an error they return -1, not some arbitrary</title>
<updated>2019-06-28T13:32:41Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-06-28T13:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=df69c215c7c66baf660f3f65414fd34796c96152'/>
<id>urn:sha1:df69c215c7c66baf660f3f65414fd34796c96152</id>
<content type='text'>
value &lt; 0.  errno is only updated in this case.  Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
</content>
</entry>
<entry>
<title>introduce 'pfctl -FR' to reset settings to defaults</title>
<updated>2019-04-15T21:36:44Z</updated>
<author>
<name>sashan</name>
<email>sashan@openbsd.org</email>
</author>
<published>2019-04-15T21:36:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=22f3d0383c550fab1db15772d0206e2bdc5e96d0'/>
<id>urn:sha1:22f3d0383c550fab1db15772d0206e2bdc5e96d0</id>
<content type='text'>
  (discussed with many at tech@)

OK deraadt@, kn@, sthen@, tedu@
</content>
</entry>
</feed>
