Re: inetd(8): cmdif as builtin

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>> In any case, the major issue I would have with it is the lack of
>> authentication.  But that's so obvious that I assume you would be
>> doing something like requiring a password - or doing it only for
>> AF_LOCAL sockets and using LOCAL_PEEREID.  [...]
> When this was done in last years GSoC it was a AF_LOCAL socket to
> control inetd.  I am not sure that inetd having a configuration
> service listening on the network is a really good idea -

I'm not sure either.  But I definitely am not sure enough that it never
could be that I would specifically forbid a configuration that, for
example, tries to activate cmdif on 10.4.77.186 or some such.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B