Re: tripwire and device numbers
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Thu, 04 Mar 2010 20:55:39 +0000
In message <201003041953.o24JrDhi038522@xxxxxxxxxxxxxx>, 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@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-security@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: tripwire and device numbers
- From: Dag-Erling Smørgrav
- Re: tripwire and device numbers
- References:
- tripwire and device numbers
- From: Mike Tancsa
- tripwire and device numbers
- Prev by Date: Re: tripwire and device numbers
- Next by Date: Re: tripwire and device numbers
- Previous by thread: Re: tripwire and device numbers
- Next by thread: Re: tripwire and device numbers
- Index(es):
Relevant Pages
|
