From owner-freebsd-questions Mon Oct 1 21:34:23 2001 Delivered-To: freebsd-questions@freebsd.org Received: from pogo.caustic.org (caustic.org [64.163.147.186]) by hub.freebsd.org (Postfix) with ESMTP id BFA7037B40A; Mon, 1 Oct 2001 21:34:14 -0700 (PDT) Received: from localhost (jan@localhost) by pogo.caustic.org (8.11.0/ignatz) with ESMTP id f924YDU77196; Mon, 1 Oct 2001 21:34:13 -0700 (PDT) Date: Mon, 1 Oct 2001 21:34:13 -0700 (PDT) From: "f.johan.beisser" To: David Kirchner Cc: default , freebsd-security@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: file permission question In-Reply-To: <20011001202424.X85958-100000@localhost> Message-ID: X-Ignore: This statement isn't supposed to be read by you MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 1 Oct 2001, David Kirchner wrote: > On Mon, 1 Oct 2001, f.johan.beisser wrote: > > Running a file integrity check such as tripwire is also a good idea - as > long as you run tripwire from a read-only floppy or something similar that > is. :-) excellent point, one that i totally flaked on. although, tripwire is only semi-preventative, it's more of a manner of making sure that someone has been able to change either binaries or directories on the server. sadly, it can't help with changed files. there are some excellent documents on 'hardening' your OS-of-choice out there, including some on hardening FreeBSD. a quick google search should turn some up. i would suggest reading some of the infomation available on SecurityFocus.com's site. -- jan -------/ f. johan beisser /--------------------------------------+ http://caustic.org/~jan jan@caustic.org "if my thought-dreams could be seen.. "they'd probably put my head in a gillotine" -- Bob Dylan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message