From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net, Jeff Layton <jlayton@redhat.com>
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 [thread overview]
Message-ID: <20070420181144.GI19285@fieldses.org> (raw)
In-Reply-To: <4d569c330704201057l1ba2a131r39df22db6e917fb3@mail.gmail.com>
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
next prev parent reply other threads:[~2007-04-20 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 14:43 svc_process and nfsd_proc_read not taking checksum into account when calling svc_reserve Jeff Layton
2007-04-20 17:47 ` J. Bruce Fields
2007-04-20 17:57 ` Kevin Coffman
2007-04-20 18:11 ` J. Bruce Fields [this message]
2007-04-20 18:33 ` Jeff Layton
2007-04-20 18:38 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070420181144.GI19285@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=kwc@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox