Re: [RFC] inetd(8) changes proposal

2023-06-01 Thread Brett Lymn
On Thu, Jun 01, 2023 at 09:08:52AM +0200, tlaro...@polynum.com wrote: > > But for now, it will be far simpler to only modify the NetBSD source > without trying to merge something external. > It isn't external - the mods were made to the NetBSD source code. -- Brett Lymn -- Sent from my NetBSD

Re: bl*cklist configuration, ssh only

2023-06-01 Thread Michael van Elst
On Thu, Jun 01, 2023 at 05:05:16PM +0100, Patrick Welche wrote: > > What puzzles me is: > > # blocklistctl dump -a | wc > 53 2182497 > > BUT: > > # npfctl rule blocklistd list | wc >3 45 254 > > Only 3 hosts apparently being blocked by npf vs 53. blocklistctl

Re: bl*cklist configuration, ssh only

2023-06-01 Thread Patrick Welche
On Tue, May 30, 2023 at 03:54:52PM -, Michael van Elst wrote: > ignat...@cs.uni-bonn.de writes: > > >Hello, > > >is there a minimal example how to configure bl*cklistd and npf to > >block attacks on sshd? > > /etc/bl*cklistd.conf: > # Bl*cklist rule > # adr/mask:port typeproto owner

mtree(8) vs mtree(5)

2023-06-01 Thread Valery Ushakov
We have mtree(8) man page for our mtree that documents the format of the mtree spec. We also have an mtree(5) page that documents the format of the mtree spec, but that pages comes from libarchive. This is kinda confusing. What is the relationship between the two? (libarchive borrowed bsd code?

Re: [RFC] inetd(8) changes proposal

2023-06-01 Thread tlaronde
Le Thu, Jun 01, 2023 at 12:50:30PM +0930, Brett Lymn a écrit : > On Wed, May 31, 2023 at 12:43:40PM +0200, tlaro...@polynum.com wrote: > > > > And I think you're right: the info will go in a 0400 file in /tmp, and > > will be a way to obtain various running infos---but for now, just the > >