Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > muc.lists.netbsd.tech.security > #231
| From | Martin Husemann <martin@duskware.de> |
|---|---|
| Newsgroups | muc.lists.netbsd.tech.security |
| Subject | Re: inetd(8): security behavior |
| Date | 2023-05-29 13:45 +0200 |
| Organization | Newsgate at muc.de e.V. |
| Message-ID | <20230529114543.GA3151@mail.duskware.de> (permalink) |
| References | <ZHRfS8HYzZEWq2nr@polynum.com> <CAGN_6pbsBzs=9tBg1P7GG33cMcQXPE-iSP50CHZEBWAV13EEdw@mail.gmail.com> |
On Mon, May 29, 2023 at 11:50:30AM +0100, David Brownlee wrote: > NetBSD tends to be more aware of historic behaviour than some other > projects, but I think this is the intersection of "behaviour is just > what came about" with "little used service, so has had less > attention". The whole key/value notation is new (and local to the NetBSD version of inetd), isn't it? So there is not much compat or historic behaviour to follow here - or am I overlooking something? I would support resetting the defaults on error and maybe even at the start of a new file (but that is debatable, in other config formats that kind of inheritance gives rope for nice admin tricks). Martin -- Posted automagically by a mail2news gateway at muc.de e.V. Please direct questions, flames, donations, etc. to news-admin@muc.de
Back to muc.lists.netbsd.tech.security | Previous | Next — Previous in thread | Find similar
inetd(8): security behavior tlaronde@polynum.com - 2023-05-29 10:16 +0200
Re: inetd(8): security behavior David Brownlee <abs@netbsd.org> - 2023-05-29 11:50 +0100
Re: inetd(8): security behavior Martin Husemann <martin@duskware.de> - 2023-05-29 13:45 +0200
csiph-web