Date: Sat, 18 Mar 2006 20:32:54 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Chris Maness <chris@chrismaness.com> Cc: freebsd-questions@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: hosts.allow ? Message-ID: <20060319013253.GA65688@xor.obsecurity.org> In-Reply-To: <441CB2D8.3090707@chrismaness.com> References: <441CA1F9.20301@chrismaness.com> <20060319004947.GA65074@xor.obsecurity.org> <441CB2D8.3090707@chrismaness.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 18, 2006 at 05:24:40PM -0800, Chris Maness wrote: > Kris Kennaway wrote: > >On Sat, Mar 18, 2006 at 04:12:41PM -0800, Chris Maness wrote: > > =20 > >>My denyhost script is doing it's job by adding: > >> > >>sshd: 62.149.232.105 : deny > >> > >>to the hosts.allow file, but I see that this host is still making=20 > >>attempts to get into my box. > >> =20 > > > >Where do you see this (i.e. logged by what)? hosts.allow doesn't > >block the IP from connecting to the port, it blocks the application > >that listens on the port from allowing this IP to authenticate. > >e.g. your firewall may still log the connection. > > > > =20 > p.s. I tried a test from another one of my host by adding a line just=20 > like the one above and it still allows me to login. Sounds like something else is wrong with your hosts.allow then. Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEHLTFWry0BWjoQKURAgtlAKCDtFye5pH/jksADrt7I528F2yEZgCfR9Ed oyHwe91tHYD8c/qxlPKmnok= =sarh -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060319013253.GA65688>