From owner-freebsd-security  Sat Mar  8 15:41:58 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA07925
          for security-outgoing; Sat, 8 Mar 1997 15:41:58 -0800 (PST)
Received: (from mpp@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA07892;
          Sat, 8 Mar 1997 15:40:43 -0800 (PST)
From: Mike Pritchard <mpp>
Message-Id: <199703082340.PAA07892@freefall.freebsd.org>
Subject: Re: 4.4BSD NFS File Handles (fwd)
To: guido@gvr.win.tue.nl (Guido van Rooij)
Date: Sat, 8 Mar 1997 15:40:43 -0800 (PST)
Cc: danny@panda.hilink.com.au, freebsd-security@freebsd.org
In-Reply-To: <199703070752.IAA01682@gvr.win.tue.nl> from "Guido van Rooij" at Mar 7, 97 08:52:18 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Guido van Rooij wrote:
> 
> Mike Pritchard wrote:
> > If I remember right, the last time I looked at how the kernel
> > assigned generation number, it didn't do a very good job
> > of it (they were pretty predictable).  We should probaby
> > change them to use the random() kernel function.
> 
> I also want to have the fsirand stuff. That should be enough. Perhaps
> it should even be built in newfs.
-- 

We also need to remove the code in ffs_alloc that sets
the generation number = the current time if it is currently less than 
the current time.  Right now, you can pretty much guess 
the generation number by loking at a files ctime and mtime fields.  
If the gen number isn't equal to one of those, then it is usually 
within some small delta of them.
--
Mike Pritchard
mpp@FreeBSD.org
"Go that way.  Really fast.  If something gets in your way, turn"