[2257] in WWW Security List Archive

home help back first fref pref prev next nref lref last post

Re: Email Hack: Help.

daemon@ATHENA.MIT.EDU (Alan Batie)
Tue Jun 25 15:00:23 1996

From: batie@aahz.jf.intel.com (Alan Batie)
To: Steff.Watkins@Bristol.ac.uk (Steff Watkins)
Date: Tue, 25 Jun 1996 09:49:25 -0700 (PDT)
Cc: WWW-SECURITY@ns2.rutgers.edu
In-Reply-To: <9606250745.AA03544@sun.cse.bris.ac.uk> from "Steff Watkins" at Jun 25, 96 08:45:08 am
Errors-To: owner-www-security@ns2.rutgers.edu

> Assuming that the systems that have email daemons are Unix-based, you can
> use the 'hosts.allow' and 'hosts.deny' mechanism.

This assumes the use of tcpwrapper, which most email daemons don't use.  It
shouldn't be hard to firewall out the offending site though, once it's
tracked down.

-- 
Alan Batie                     ------        What goes up, must come down.
batie@aahz.jf.intel.com        \    /        Ask any system administrator.
+1 503-264-8844 (voice)         \  /         --unknown
D0 D2 39 0E 02 34 D6 B4          \/          5A 41 21 8F 23 5F 08 9D

home help back first fref pref prev next nref lref last post