Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Mar 2010 20:55:39 +0000
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Mike Tancsa <mike@sentex.net>
Cc:        freebsd-security@freebsd.org
Subject:   Re: tripwire and device numbers 
Message-ID:  <3402.1267736139@critter.freebsd.dk>
In-Reply-To: Your message of "Thu, 04 Mar 2010 14:53:24 EST." <201003041953.o24JrDhi038522@lava.sentex.ca> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <201003041953.o24JrDhi038522@lava.sentex.ca>, Mike Tancsa writes:

>While getting a box ready for deployment, I noticed on two occasions, 
>I would get some exception reports flagging all files as the 
>underlying device number through reboots had changed.  Is this 
>"normal" for Tripwire and FreeBSD ? (RELENG_7)

Yes, device numbers in freebsd carry no meaning,  unless it is
a compat /dev directory to boot ancient systems (SunOS, very
old FreeBSD etc) diskless.

In general, tripwire should ignore devfs and possibly all pseudo-fs
mount-points.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3402.1267736139>