[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-security] Difference between hosts.deny and ipchains DENY
- Subject: Re: [cobalt-security] Difference between hosts.deny and ipchains DENY
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Jan 2002 14:03:46 +0000 (GMT)
- List-id: Mailing list for users to address network security on Cobalt products. <cobalt-security.list.cobalt.com>
> Date: Mon, 21 Jan 2002 12:39:12 -0500
> From: Gerald Waugh <gerald@xxxxxxxxx>
> host.deny works for inetd processes (sshd, proftpd,
hosts.deny
> qpopper) maybe a few more. ipchains works at the kernel
> level. If you block with ipchains, it may save some resources.
Note that some programs, including sshd, can be compiled with
TCP wrapper (official name for using hosts.allow and hosts.deny)
support even if run as a daemon, as opposed to being started via
inetd.
> Gerald Waugh
> Registered Linux User 255245
> register at http://counter.li.org
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots. Do NOT
send mail to <blacklist@xxxxxxxxx>, or you are likely to be blocked.