From owner-freebsd-current Thu Aug 2 12:31: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 1823A37B405 for ; Thu, 2 Aug 2001 12:31:07 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 15SOBV-00001c-00; Thu, 2 Aug 2001 21:31:05 +0200 Received: (from daemon@localhost) by kemoauc.mips.inka.de (8.11.4/8.11.1) id f72IT1Z04355 for freebsd-current@freebsd.org; Thu, 2 Aug 2001 20:29:01 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: What's touching my executables? Date: Thu, 2 Aug 2001 18:28:59 +0000 (UTC) Message-ID: <9kc65b$47n$1@kemoauc.mips.inka.de> Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -CURRENT (Jul 25), alpha. An increasing number of executables on that box are sporting ever newer mtimes. This appears to have been going on ever since the Jul 25 update. There is no clear pattern which executables are touched. md5 comparisons with previous backup levels (using a Jul 13 copy of md5) suggest that the executables have not been changed. For various reasons I consider it unlikely that I'm dealing with a security issue here, although I'm looking into that as well. Can anybody think of a technical explanation? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message