Date: Wed, 15 Mar 2000 22:13:44 -0800 From: Doug Barton <Doug@gorean.org> To: Lawrence Sica <larry@interactivate.com> Cc: Rodrigo Campos <camposr@MATRIX.COM.BR>, freebsd-security@FreeBSD.ORG Subject: Re: wrapping sshd Message-ID: <38D07B98.53CBA3E@gorean.org> References: <Pine.BSF.4.21.0003151730240.11873-100000@speed.matrix.com.br> <38D00906.389A9A28@interactivate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Lawrence Sica wrote:
> sshd can do this within it's own config file already.
True, but I've always found it more convenient to have all of my system
access limits in the same file. (Well, two files, hosts.allow and
rc.firewall, so I really don't want a third...)
> The reasons for not
> running it in inetd are pretty much the same for not wrapping it.
No, not running it out of inetd is a whole different issue. The theory
is that sshd is more reliable than inetd, and you always want to be able
to get into your system. I have always thought that the sshd authors
were a bit grandiose on that topic.. :)
Doug
--
"While the future's there for anyone to change, still you know it
seems,
it would be easier sometimes to change the past"
- Jackson Browne, "Fountain of Sorrow"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38D07B98.53CBA3E>