From owner-freebsd-hackers Wed Aug 9 15: 6:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DB4AA37B95D; Wed, 9 Aug 2000 15:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA53520; Wed, 9 Aug 2000 15:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 9 Aug 2000 15:06:45 -0700 (PDT) From: Kris Kennaway To: =?iso-8859-1?B?SmVz+nMgQXJu4Wl6?= Cc: freebsd-hackers Subject: Re: Logging changes in files. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, [iso-8859-1] Jes=FAs Arn=E1iz wrote: > Hi Everyone! >=20 > I'm using FreeBSD and I'm interesting in log when a user modifies some fi= le > and the changes made on it. See the kqueue(2) manpage in FreeBSD 4.1. It would be a trivial matter to write a utility that watches files for activity and logs it, although finding out who modified the file would be harder. The "proper" way to do this is using a kernel event audit system, which is something the TrustedBSD project (www.trustedbsd.org) will provide, but AFAIK no code is available for this yet. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message