Date: Tue, 12 Aug 1997 09:57:02 -0600 From: Kenneth Ingham <ingham@i-pi.com> To: Jeff Aitken <jaitken@aitken.com> Cc: security@freebsd.org Subject: Re: post-break-in checklist? Message-ID: <19970812095702.20181@socrates.i-pi.com> In-Reply-To: <199708120324.XAA27102@eagle.aitken.com>; from Jeff Aitken on Mon, Aug 11, 1997 at 11:24:34PM -0400 References: <199708120324.XAA27102@eagle.aitken.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> As far as FreeBSD goes, I've got the CDs and know about mtree, but > I'm looking for a more generic "these are the sorts of things to > look for if you suspect a security violation" just to be sure I'm > not overlooking anything. While it's not a post-breakin tool, tripwire can help identify breakins. The URL for Coast at Purdue (where it was developed) is: http://www.cs.purdue.edu/coast/ Kenneth Ingham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970812095702.20181>