Re: inetd(8): security considerations

2023-07-03 Thread Mouse
> [...], putting the file only under root writability is a safety > precaution too (against one's own blunders). > There are pros and cons either way---meaning that, you are right, it > has to be configurable; remains the question of: what should be the > default? Strict or not? Hmm. For NetBSD

Re: inetd(8): security considerations

2023-07-03 Thread tlaronde
Le Mon, Jul 03, 2023 at 08:36:23AM -0400, Mouse a écrit : > > There is one more thing I'd be inclined to add: when _serving_ a > > config as root[*], error if the configuration (including sourced > > chunks) is writable by someone else than root. > > > What do you think? > > A reasonable thing if

Re: inetd(8): security considerations

2023-07-03 Thread Mouse
> There is one more thing I'd be inclined to add: when _serving_ a > config as root[*], error if the configuration (including sourced > chunks) is writable by someone else than root. > What do you think? A reasonable thing if it's an overridable default. An extremely annoying thing (albeit only

inetd(8): security considerations

2023-07-03 Thread tlaronde
I'm almost finished with inetd(8)---I still wait for an answer about ATF tests: to be added if my version of inetd will reach the NetBSD src tree; if not reaching the NetBSD src tree, I will not bother with ATF. There is one more thing I'd be inclined to add: when _serving_ a config as root[*], er