acme-client.1 - Change "TLS certificate" to "X.509 certificate"

It's an "X.509 certificate" rather than a "TLS certificate". As pointed out by sthen@, TLS isn't the only possible use. Index: acme-client.1 === RCS file: /cvs/src/usr.sbin/acme-client/acme-client.1,v retrieving revision 1.24

acme-client.1 - fix mangled sentence and stray plural

This is the first of several diffs containing separate bits of the earlier combined diff. "X509" to "X.509" for correctness and consistency with acme-client.conf.5 Index: acme-client.1 === RCS file:

Re: correct nd6_timer_next accounting

Running your diff on both my APU2 and X250, I no longer see NDP entries staying expired, so this is an improvement! More tests and review tomorrow, thanks for looking into this.

Re: Floating point exception on boot after using syspatch(8)

On Wed, 1 Aug 2018, Zbyszek Żółkiewski wrote: > OpenBSD 6.3 GENERIC.MP running on XEN (AWS m4.large) - dmesg at the end > of this mail. Image build from https://github.com/kolargol/openbsd-aws > which is fork from https://github.com/ajacoutot/aws-openbsd - my fork > have some minor

properly delete eigrpd(8)'s unix socket on shutdown

Hi, Currently the eigrp engine process from eigrpd(8) runs in a chroot and at the same time the unlink(socket) is called when its shutdown, of course this won't work because the file won't be found within the chroot environment. To solve this the patch below brings the control_cleanup() function

fix use-after-free on eigrpd(8)

Hi, eigrpd(8) should only free the configured interfaces after the eigrp instances on shutdown otherwise an use after free will happen and the name of the iface will also not be displayed since that information was already disposed. The use-after-free actually doesn't manifest everytime, but

Regulator ramp delay

Ramping up the voltage of a regulator takes time; the target voltage is not reached instantaniously. And typically you should not continue until the target voltage has been reached. For example, if we want to increase the clock speed of a CPU, we typically also need to increase the voltage. And

Re: [PATCH] jot(1): negative and overflowing reps

On Tue, Jul 31, 2018 at 05:38:20PM -0500, Kris Katterjohn wrote: > On Wed, Aug 01, 2018 at 12:24:59AM +0200, Theo Buehler wrote: > > ok tb if anyone wants to commit. > > Cool, thanks for looking at this. > > > > + errx(1, "Bad reps value, %s: %s", errstr, > > > > A

Re: ssdfb(4): SSD1309 OLED display (128x64)

On Tue, Jul 31, 2018 at 03:05:11PM +0200, Mark Kettenis wrote: > You might want to look at what the udl(4) driver does. The kernel > driver lives in sys/dev/usb/udl.c and implements a "damage" ioctl that > updates a region of the actual framebuffer from the virtual > framebuffer that lives in

Re: fix segfault on radiusd(8)

:facepalm: let's forget I sent the previous patch. OK? Index: radiusd.c === RCS file: /cvs/src/usr.sbin/radiusd/radiusd.c,v retrieving revision 1.20 diff -u -p -u -r1.20 radiusd.c --- radiusd.c 13 Jun 2017 05:40:22 - 1.20

Re: fix segfault on radiusd(8)

On Wed, Aug 01, 2018 at 12:54:49PM +0100, Ricardo Mestre wrote: > Hi, > > When radiusd(8) starts shutting down one of the actions is to iterate through > the configured modules and freezero(3) each module->secret. By using the > config > from /etc/examples/radiusd.conf which has module bsdauth

Re: fix segfault on radiusd(8)

Forgot to mention that I didn't use an if (module->secret != NULL) since it may look like the problem would be with freezero(3) which is not the case because this one accepts a NULL pointer without issues. On 12:54 Wed 01 Aug , Ricardo Mestre wrote: > Hi, > > When radiusd(8) starts shutting

[diff] Improvements for acme-client.1, acme-client.conf.5

acme-client.1 changes are largely similar to my previous attempt [off-list] with some feedback from jsing@ [thanks!] The example has been changed from "example.com" to "www.example.com" in an attempt to make it clear that "domain" is a misnomer. acme-client.conf.5 stuff is mostly documenting

Floating point exception on boot after using syspatch(8)

Hi guys, OpenBSD 6.3 GENERIC.MP running on XEN (AWS m4.large) - dmesg at the end of this mail. Image build from https://github.com/kolargol/openbsd-aws which is fork from https://github.com/ajacoutot/aws-openbsd - my fork have some minor modifications. Recently i run into problems after using

add pledge(2) to relayd(8)'s main proc

Hi, This add pledge(2) to the main proc of relayd(8) with the following promises: - rpath: load (and reload) the config file - cpath: unlink the RELAYD_SOCKET - inet/dns: the daemon deals with AF_INET sockets and also needs to resolve dns - sendfd: send fds to its childs - unix: additionaly if

Re: [PATCH] find(1) man page, source comment: assumed -print

On Wed, Aug 01, 2018 at 07:19:13AM +0100, Jason McIntyre wrote: > On Mon, Jul 30, 2018 at 05:19:40PM -0500, Kris Katterjohn wrote: > > Hey, > > > > A statement in the find(1) man page and a source comment in find.c are > > outdated and incorrect. > > > > The man page didn't mention that using