Date: Sun, 8 Oct 2000 22:50:26 -0700 From: Kris Kennaway <kris@citusc.usc.edu> To: Doug Barton <DougB@gorean.org> Cc: Jordan Hubbard <jkh@winston.osd.bsdi.com>, Matt Dillon <dillon@earth.backplane.com>, Warner Losh <imp@village.org>, Jeroen Ruigrok van der Werven <jruigrok@via-net-works.nl> Subject: Re: cvs commit: src/etc inetd.conf Message-ID: <20001008225026.D39735@citusc17.usc.edu> In-Reply-To: <39E15B3C.80560313@gorean.org>; from DougB@gorean.org on Sun, Oct 08, 2000 at 10:44:28PM -0700 References: <521.971068411@winston.osd.bsdi.com> <39E15630.7B4A8FE6@gorean.org> <20001008223626.B39735@citusc17.usc.edu> <39E15B3C.80560313@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 08, 2000 at 10:44:28PM -0700, Doug Barton wrote: > Kris Kennaway wrote: > > > > On Sun, Oct 08, 2000 at 10:22:56PM -0700, Doug Barton wrote: > > > > > ERrr... the argument that telnet should be available from inetd because > > > a worker might be coming to a job with the wrong tools isn't valid. A > > > better argument to allow telnet is that sshd requires some > > > configuration, and telnet doesn't. > > > > Nope, sshd doesn't require any configuration to be usable and useful > > out of the box. > > Currently the necessary configuration happens behind the scenes, hidden > behind the rc* magic. (Not that I'm arguing that this is a bad thing, > necessarily.) But sshd does need some configuration before it is > runnable. I don't understand what you're saying. When a box is installed, and rebooted for the first time, both telnetd and sshd emerge in a usable state with no other intervention required. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001008225026.D39735>