Re: EVFILT_TIMER add support for different timer precisions NOTE_{,U,N,M}SECONDS

2023-08-04 Thread A Tammy
On 8/5/23 00:49, Scott Cheloha wrote: > On Sat, Aug 05, 2023 at 12:17:48AM -0400, aisha wrote: >> On 22/09/10 01:53PM, Visa Hankala wrote: >>> On Wed, Aug 31, 2022 at 04:48:37PM -0400, aisha wrote: I've added a patch which adds support for NOTE_{,U,M,N}SECONDS for EVFILT_TIMER in the

Re: EVFILT_TIMER add support for different timer precisions NOTE_{,U,N,M}SECONDS

2023-08-04 Thread Scott Cheloha
On Sat, Aug 05, 2023 at 12:17:48AM -0400, aisha wrote: > On 22/09/10 01:53PM, Visa Hankala wrote: > > On Wed, Aug 31, 2022 at 04:48:37PM -0400, aisha wrote: > > > I've added a patch which adds support for NOTE_{,U,M,N}SECONDS for > > > EVFILT_TIMER in the kqueue interface. > > > > It sort of

Re: EVFILT_TIMER add support for different timer precisions NOTE_{,U,N,M}SECONDS

2023-08-04 Thread aisha
On 22/09/10 01:53PM, Visa Hankala wrote: > On Wed, Aug 31, 2022 at 04:48:37PM -0400, aisha wrote: > > I've added a patch which adds support for NOTE_{,U,M,N}SECONDS for > > EVFILT_TIMER in the kqueue interface. > > It sort of makes sense to add an option to specify timeouts in > sub-millisecond

Re: ldd: check read return value to avoid unitialized struct fields [was "ldd: check {,p}read return

2023-08-04 Thread Theo de Raadt
Lucas wrote: > Bump. > > Lucas wrote: > > Now with a better subject. > > > > I was also wondering about the lack of pledge() other than the newly > > added one. That goes because dlopen() can do anything? > > > > Lucas wrote: > > > Hi, > > > > > > I wanted to understand how the pledge

Re: ldd: check read return value to avoid unitialized struct fields [was "ldd: check {,p}read return

2023-08-04 Thread Lucas
Bump. Lucas wrote: > Now with a better subject. > > I was also wondering about the lack of pledge() other than the newly > added one. That goes because dlopen() can do anything? > > Lucas wrote: > > Hi, > > > > I wanted to understand how the pledge execpromises commit worked in ldd > > and

Re: sec(4): route based ipsec vpns

2023-08-04 Thread Bryce Chidester
This is very exciting! Lack of support for route-based IPsec VPNs in OpenBSD has been a major bummer. I'm hopeful this work will eventually make it into OpenBSD. I did some basic testing of this patch with an AWS site-to-site VPN (it was convenient) and it seems to work well. "ifconfig secX down"

Re: bgpd, be more carefule with shutdown reason

2023-08-04 Thread Theo de Raadt
Theo Buehler wrote: > On Fri, Aug 04, 2023 at 11:40:36AM +0200, Claudio Jeker wrote: > > When copying the shutdown reason from ctl_neighbor into the peer struct > > the strlcpy needs a NUL terminated string input. This may not be the case > > so we should be more careful here. > > I see two ways

installer: always create new softraid volume

2023-08-04 Thread Klemens Nanni
If the root disk contains a valid CRYPTO volume, bioctl(8) by default unlocks that instead of creating a new one. Use `-C force' to prevent reuse of old volumes, which happens if you, e.g. restart an encrypted installation past this point or install onto an old disk without wiping it first:

Re: buffer overprint in riscv64/cpu.c

2023-08-04 Thread Peter J. Philipp
On Tue, Aug 01, 2023 at 01:43:36PM +0200, p...@delphinusdns.org wrote: > >Synopsis:non-terminated strings buffer in riscv64/cpu.c > >Category:kernel > >Environment: > System : OpenBSD 7.3 > Details : OpenBSD 7.3-current (GENERIC.MP) #376: Thu Jul 13 > 03:59:40 MDT

Re: bgpd, be more carefule with shutdown reason

2023-08-04 Thread Theo Buehler
On Fri, Aug 04, 2023 at 11:40:36AM +0200, Claudio Jeker wrote: > When copying the shutdown reason from ctl_neighbor into the peer struct > the strlcpy needs a NUL terminated string input. This may not be the case > so we should be more careful here. > I see two ways to fix this. > a) force in a

bgpd, be more carefule with shutdown reason

2023-08-04 Thread Claudio Jeker
When copying the shutdown reason from ctl_neighbor into the peer struct the strlcpy needs a NUL terminated string input. This may not be the case so we should be more careful here. I see two ways to fix this. a) force in a NUL before callin strlcpy() as done below. b) use memcpy() and then force

Re: vmd: handle EAGAIN from imsg_flush

2023-08-04 Thread Claudio Jeker
On Thu, Aug 03, 2023 at 07:01:51PM -0400, Dave Voutila wrote: > > Claudio Jeker writes: > > > On Thu, Aug 03, 2023 at 04:20:47PM -0400, Dave Voutila wrote: > >> Found this while working on some virtio stuff. My original > >> implementation as part of the multi-process redesign didn't handle if