From: Jim Rees <rees@umich.edu>
To: Andy Adamson <andros@netapp.com>
Cc: Jonathan Manton <jmanton@illinois.edu>, linux-nfs@vger.kernel.org
Subject: Re: Kerberized NFS (v3 and v4) does not work if Kerberos token is >= 2048 bytes (if PAGE_SIZE == 4096)
Date: Wed, 4 Aug 2010 11:45:33 -0400 [thread overview]
Message-ID: <20100804154533.GA13950@merit.edu> (raw)
In-Reply-To: <D17BAFDB-6B3B-40B6-9C28-5689D18FBBA5@netapp.com>
Andy Adamson wrote:
> When a user with a Kerberos token of 2048 bytes or larger attempts to
> access a filesystem mounted using Kerberized NFS, the NFS server locks up
> for 30 seconds, and ultimately the call fails.
Yes, this limitation has been known for a long time. We ran into this same
issue using X.509 certs and spkm3. I imagine PKINIT will also hit this
limitation.
But shouldn't it fail right away instead of locking up for 30 seconds?
Does the entire server lock up, or just that one rpc?
Can a malicious client use this as a DOS? Does it require a valid ticket,
or will any ticket >= 2048 do?
next prev parent reply other threads:[~2010-08-04 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 14:38 Kerberized NFS (v3 and v4) does not work if Kerberos token is >= 2048 bytes (if PAGE_SIZE == 4096) Jonathan Manton
2010-08-04 15:28 ` Andy Adamson
2010-08-04 15:45 ` Jim Rees [this message]
2010-08-04 16:22 ` Jonathan Manton
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=20100804154533.GA13950@merit.edu \
--to=rees@umich.edu \
--cc=andros@netapp.com \
--cc=jmanton@illinois.edu \
--cc=linux-nfs@vger.kernel.org \
/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