From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: svc_process and nfsd_proc_read not taking checksum into
	account when calling svc_reserve
Date: Fri, 20 Apr 2007 14:11:44 -0400
Message-ID: <20070420181144.GI19285@fieldses.org>
References: <4628D19F.5080805@redhat.com> <20070420174748.GG19285@fieldses.org>
	<4d569c330704201057l1ba2a131r39df22db6e917fb3@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net, Jeff Layton <jlayton@redhat.com>
To: Kevin Coffman <kwc@citi.umich.edu>
In-Reply-To: <4d569c330704201057l1ba2a131r39df22db6e917fb3@mail.gmail.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Fri, Apr 20, 2007 at 01:57:55PM -0400, Kevin Coffman wrote:
> On 4/20/07, J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> >You don't need to know the exact amount, just an upper bound, right?
> >
> >In which case I'd be tempted to just look at some krb5i and krb5p
> >traffic in wireshark, figure out how much it adds (it should always be
> >the same, except that krb5p pads the arguments to the nearest 8-byte
> >boundary, which will add padding that varies between 1 and 8 bytes.)
> 
> Is the length going to depend on the Kerberos encryption-type as well?

Yep.  But for now we can just hard-code a constant that works for
des-cbc-whatever-it-is, with a note that some day we should increase the
constant or (if we really need it to be a tight bound on the length),
replace it by a call to the gssapi code.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs