Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: nfs@lists.sourceforge.net, Kevin Coffman <kwc@citi.umich.edu>
Subject: Re: svc_process and nfsd_proc_read not taking checksum into account when calling svc_reserve
Date: Fri, 20 Apr 2007 14:38:38 -0400	[thread overview]
Message-ID: <20070420183838.GJ19285@fieldses.org> (raw)
In-Reply-To: <46290789.7080908@redhat.com>

On Fri, Apr 20, 2007 at 02:33:45PM -0400, Jeff Layton wrote:
> Thanks for the info. I'll shoot for just having the wrapper add a 
> constant value to it for now (though I'll at least get the auth flavor 
> and set that value to 0 for auth_null and auth_unix).
> 
> I tested krb5p and it seems to be off by 52 bytes, but I was using 
> des-cbc-crc:normal. Got a suggestion of what kerberos enc type I should 
> use to try to maximize the length?

That's all we've got in mainline right now--the others are only in
experimental 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

      reply	other threads:[~2007-04-20 18:38 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
2007-04-20 18:33       ` Jeff Layton
2007-04-20 18:38         ` J. Bruce Fields [this message]

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=20070420183838.GJ19285@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