From: <whats_up@gmx.net>
To: steve <steve@steve-ss.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mount hangs in NFS4+Kerberos setup
Date: Fri, 10 Feb 2012 18:41:54 +0100 [thread overview]
Message-ID: <20120210184154.03fb6907@little-poseidon> (raw)
In-Reply-To: <4F35512A.9050500@steve-ss.com>
> Some older kernels do not support strong keys. Try adding:
> allow_weak_crypto = true
> to the
> [libdefaults]
> in /etc/krb5.conf
yes. I painfully (mount only says access denied) found out this already
and I use allow_weak_crypto to limit to DES. More encryption
types have been introduced with kernel 2.6.39...
I tried to use kernel 3.2 from squeeze-backports but this introduced new
errors, thus I decided to try with 2.6 first.
> Also it's not recommended to use the pseudo-root fsid=0 method for
> nfs exports under Linux:
> http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
hmm, as far as I have understood I have to:
- export the root folder /exports explicitly beside the "real"
exports p.ex. /exports/opt
- use fsid=0 for the root folder to force version 4 of NFS
What's your suggestion to improve/secure my configuration?
regards
knut
next prev parent reply other threads:[~2012-02-10 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:45 mount hangs in NFS4+Kerberos setup whats_up
2012-02-10 14:52 ` Sven Geggus
2012-02-10 15:36 ` Andy Adamson
[not found] ` <20120210172554.5e89e364@little-poseidon>
2012-02-10 18:19 ` Andy Adamson
2012-02-13 9:32 ` whats_up
2012-02-10 17:17 ` steve
2012-02-10 17:41 ` whats_up [this message]
2012-02-10 18:07 ` steve
2012-02-10 18:21 ` Daniel Kahn Gillmor
2012-02-10 18:51 ` J. Bruce Fields
2012-02-10 19:06 ` steve
2012-02-10 19:13 ` J. Bruce Fields
2012-02-13 10:01 ` whats_up
2012-02-13 10:51 ` Sven Geggus
2012-02-13 18:50 ` whats_up
2012-02-13 18:55 ` Daniel Kahn Gillmor
2012-02-15 9:57 ` Sven Geggus
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=20120210184154.03fb6907@little-poseidon \
--to=whats_up@gmx.net \
--cc=linux-nfs@vger.kernel.org \
--cc=steve@steve-ss.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.