From owner-freebsd-security Sat May 4 15:50:10 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA07504 for security-outgoing; Sat, 4 May 1996 15:50:10 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA07497 for ; Sat, 4 May 1996 15:50:07 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id RAA00682; Sat, 4 May 1996 17:49:32 -0500 (EST) From: "John S. Dyson" Message-Id: <199605042249.RAA00682@dyson.iquest.net> Subject: Re: Weird system security output To: batsy@groovy.dreaming.org (jamie) Date: Sat, 4 May 1996 17:49:32 -0500 (EST) Cc: brian@mail.vividnet.com, freebsd-security@FreeBSD.ORG In-Reply-To: from "jamie" at May 4, 96 06:31:10 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have had this happen and have rationalized it, but I'm not sure if it > is a cause. I always thought that it was because of the sup process > adding new files and updating current ones. If I'm dead wrong please > correct me. > There IS a bug in -stable (might have been fixed recently) that modified dates on executables can get modified during paging. We just found a very subtile bug in pmap.c (it might be in the asm statements or in the register allocation associated with them), that appears to have been fixed when we rewrote the code. The bug that appears to have been fixed also could have been manifested by changed modify dates. This is a very very tough one. John