Re: What's touching my executables?

[Will Andrews]

On Thu, Aug 02, 2001 at 06:28:59PM +, Christian Weisgerber ([EMAIL PROTECTED]) 
wrote:
 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?

Probably the recent change (IIRC) that someone turned running an
executable into a mtime change.

-- 
wca

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: What's touching my executables?

[Christian Weisgerber]

Will Andrews [EMAIL PROTECTED] wrote:

 Probably the recent change (IIRC) that someone turned running an
 executable into a mtime change.

That was about _atime_ and the discussion was still going on after
I last updated the box.  Besides, I verified that simply running
an executable does not lead to an mtime change.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message