Re: rpki-client: ensure X.509 Subject only contains commonName and serialNumber

2023-09-11 Thread Theo Buehler
On Mon, Sep 11, 2023 at 01:42:03AM +, Job Snijders wrote: > This adds another compliance check for the X.509 subject name. > > Only commonName, and optionally serialNumber, are permitted in the > certificate subject name. See RFC 6487 section 4.4 and 4.5. > > It seems the one CA who was not

Re: ps.1/kvm documentation

2023-09-11 Thread Stuart Henderson
-H is userland threads, -k is kernel threads. I guess "kernel visible" was to distinguish between the old uthread where threads were handled in userland and not visible to the kernel, and rthread ... -- Sent from a phone, apologies for poor formatting. On 11 September 2023 10:02:32 Marc

ps.1/kvm documentation

2023-09-11 Thread Marc Espie
I was reading through ps.1, which has two slightly different options -H Also display information about kernel visible threads. -k Also display information about kernel threads. It's not at all obvious what the difference between these options might be. >From the log:

Re: ps.1/kvm documentation

2023-09-11 Thread Claudio Jeker
On Mon, Sep 11, 2023 at 11:02:00AM +0200, Marc Espie wrote: > I was reading through ps.1, which has two slightly different options > -H Also display information about kernel visible threads. > -k Also display information about kernel threads. > > It's not at all obvious what

path: speed-up pkg-config

2023-09-11 Thread Marc Espie
Not to pkgconf levels, but still way faster than what we had Updated patch from what I've shown to people, turns out the second grep wasn't quite working. This does cache the set_variables_from_env shennanigans, speeding up large processing of recursive files by a large factor (since we keep a

Re: ps.1/kvm documentation

2023-09-11 Thread Marc Espie
On Mon, Sep 11, 2023 at 11:00:41AM +0100, Stuart Henderson wrote: > -H is userland threads, -k is kernel threads. I guess "kernel visible" was > to distinguish between the old uthread where threads were handled in > userland and not visible to the kernel, and rthread ... > > -- > Sent from a

Re: ps.1/kvm documentation

2023-09-11 Thread Marc Espie
On Mon, Sep 11, 2023 at 12:10:17PM +0200, Claudio Jeker wrote: > On Mon, Sep 11, 2023 at 11:02:00AM +0200, Marc Espie wrote: > > I was reading through ps.1, which has two slightly different options > > -H Also display information about kernel visible threads. > > -k Also

Re: Dell R7615 kernel protection fault

2023-09-11 Thread Hrvoje Popovski
On 11.9.2023. 6:27, Hrvoje Popovski wrote: > On 11.9.2023. 2:48, Mike Larkin wrote: >> On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote: >>> Hi all, >>> >>> I've installed latest snapshot with uefi on Dell R7615 with AMD EPYC >>> 9554P, with some NVMe disks on BOSS-N1 adapter and

Re: Dell R7615 kernel protection fault

2023-09-11 Thread Mike Larkin
On Mon, Sep 11, 2023 at 03:23:28PM +0200, Hrvoje Popovski wrote: > On 11.9.2023. 6:27, Hrvoje Popovski wrote: > > On 11.9.2023. 2:48, Mike Larkin wrote: > >> On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote: > >>> Hi all, > >>> > >>> I've installed latest snapshot with uefi on Dell

Re: Use counters_read(9) from ddb(4)

2023-09-11 Thread Martin Pieuchot
On 06/09/23(Wed) 23:13, Alexander Bluhm wrote: > On Wed, Sep 06, 2023 at 12:23:33PM -0500, Scott Cheloha wrote: > > On Wed, Sep 06, 2023 at 01:04:19PM +0100, Martin Pieuchot wrote: > > > Debugging OOM is hard. UVM uses per-CPU counters and sadly > > > counters_read(9) needs to allocate memory.

Re: rpki-client: ensure X.509 Subject only contains commonName and serialNumber

2023-09-11 Thread Job Snijders
On Mon, Sep 11, 2023 at 09:31:03AM +0200, Theo Buehler wrote: > > - * This only parses the RFC 3779 extensions since these are necessary for > > - * validation. > > Isn't this still true? You don't really parse the subject name. I took 'parse' to mean something like 'inspects', and since it also

Re: simple pledge for xeyes(1)

2023-09-11 Thread Thomas Frohwein
On Fri, Sep 08, 2023 at 08:55:10AM -0300, Lucas de Sena wrote: [...] > Quoting from `xenocara/app/xclock/xclock.c`: > > > { > > /* force reading of XErrorDB into memory to avoid adding "rpath" to > >pledge below */ > > char buf[1]; > > > >

Re: rpki-client: ensure X.509 Subject only contains commonName and serialNumber

2023-09-11 Thread Theo Buehler
On Tue, Sep 12, 2023 at 12:03:01AM +, Job Snijders wrote: > On Mon, Sep 11, 2023 at 09:31:03AM +0200, Theo Buehler wrote: > > > - * This only parses the RFC 3779 extensions since these are necessary for > > > - * validation. > > > > Isn't this still true? You don't really parse the subject

Re: ksh(1): implement p_tv() with p_ts()

2023-09-11 Thread Theo Buehler
On Mon, Sep 11, 2023 at 10:10:49PM -0500, Scott Cheloha wrote: > p_tv() is identical to p_ts() in every way except for the subsecond > conversion constants. > > Better to write p_ts() once: in p_tv(), convert from timeval to > timespec and call p_ts(). While this looks like an improvement to me,

ksh(1): implement p_tv() with p_ts()

2023-09-11 Thread Scott Cheloha
p_tv() is identical to p_ts() in every way except for the subsecond conversion constants. Better to write p_ts() once: in p_tv(), convert from timeval to timespec and call p_ts(). ok? Index: c_sh.c === RCS file:

Re: ps.1/kvm documentation

2023-09-11 Thread Philip Guenther
On Mon, Sep 11, 2023 at 5:29 AM Marc Espie wrote: > On Mon, Sep 11, 2023 at 12:10:17PM +0200, Claudio Jeker wrote: > > On Mon, Sep 11, 2023 at 11:02:00AM +0200, Marc Espie wrote: > > > I was reading through ps.1, which has two slightly different options > > > -H Also display