Date: Sun, 13 Sep 1998 10:47:06 +0200 From: sthaug@nethelp.no To: marquis@roble.com Cc: freebsd-security@FreeBSD.ORG Subject: Re: sshd Message-ID: <20632.905676426@verdi.nethelp.no> In-Reply-To: Your message of "Sat, 12 Sep 1998 19:59:58 -0700 (PDT)" References: <Pine.SUN.3.96.980912195112.21513A-100000@roble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> If you're running inetd then it doesn't seem consistent to start > daemons that don't need to run all the time from startup scripts. > Inetd was designed to conserve memory. If you have it why not use it? > /etc/inetd.conf is also a common place to implement access control (via > tcp_wrappers). But I *do* need sshd all the time :-) Starting it from inetd might make sense if this is a host you login to very rarely. > Other than that I've frequently run into situations where keepalives > had to be turned off. In those cases ssh sessions invariably die and > their daemons have to be killed-off by hand (kill <PID>). As it is > difficult to tell the original daemon from the child daemons it's also > easy to accidentally kill the parent. Not really. "cat /var/run/sshd.pid" tells you the pid of the parent. Steinar Haug, Nethelp consulting, sthaug@nethelp.no 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?20632.905676426>