Date: Mon, 20 Mar 2006 11:04:57 +0700 (ICT) From: Olivier Nicole <on@cs.ait.ac.th> To: wsantee@gmail.com Cc: freebsd@orchid.homeunix.org, freebsd-questions@freebsd.org Subject: Re: hosts.allow ? Message-ID: <200603200404.k2K44vK8063137@banyan.cs.ait.ac.th> In-Reply-To: <441D9897.7050409@gmail.com> (message from Wes Santee on Sun, 19 Mar 2006 09:44:55 -0800) References: <441CA1F9.20301@chrismaness.com> <5ceb5d550603190128q5f3e46c3o84e4b45236df0883@mail.gmail.com> <441D71FE.2070003@chrismaness.com> <200603191032.21530.gerard@seibercom.net> <441D8695.2000005@orchid.homeunix.org> <441D9897.7050409@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm not sure this is correct. If you read sshd(8), you'll see in the > FILES section that sshd will read /etc/hosts.allow and /etc/hosts.deny > on its own (i.e. it's compiled/linked with libwrap). Looking at > /usr/src/crypto/openssh/Makefile.in for the sshd target verifies this. That and sshd will re-read the file at each new connection or as soon as the file is changed. You don't need any signal/restarting of sshd to make the new wrapping policy effective. Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603200404.k2K44vK8063137>