Date: Fri, 05 Mar 2010 12:59:07 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: freebsd-security@freebsd.org Subject: Re: tripwire and device numbers Message-ID: <863a0f569g.fsf@ds4.des.no> In-Reply-To: <3402.1267736139@critter.freebsd.dk> (Poul-Henning Kamp's message of "Thu, 04 Mar 2010 20:55:39 %2B0000") References: <3402.1267736139@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
"Poul-Henning Kamp" <phk@phk.freebsd.dk> writes: > Mike Tancsa <mike@sentex.net> 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. Nothing to do with devfs; IIUC, tripwire is complaining about st.st_dev on regular files and directories. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?863a0f569g.fsf>