Date: Sun, 23 Mar 2008 21:53:34 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Andy Christianson <achristianson@orases.com> Cc: freebsd-bugs@freebsd.org Subject: RE: random st_birthtime Message-ID: <20080323215108.F66259@delplex.bde.org> In-Reply-To: <776B93361B7BEE4FAD9E720FFBC746B6BDDB68@34093-EVS4C2.exchange.rackspace.com> References: <776B93361B7BEE4FAD9E720FFBC746B6BDDB63@34093-EVS4C2.exchange.rackspace.com> <20080321130531.R58941@delplex.bde.org> <776B93361B7BEE4FAD9E720FFBC746B6BDDB68@34093-EVS4C2.exchange.rackspace.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Mar 2008, Andy Christianson wrote: >> Yes, these are 2 of many which weren't updated when birthtime was >> added. > > Thank you for the info. Now I understand why it is happening. > Would this cause any issues other than the minor security > issue of exposing random pieces of memory? Just nothing being able to trust st_birthtime. Applications would have to do something like statfs() to see if the file system is one of the ones that supports st_birthtime (blacklist the others), but since no one seemed to notice this bug before I doubt that any applications know to do this. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080323215108.F66259>