public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: <whats_up@gmx.net>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mount hangs in NFS4+Kerberos setup
Date: Mon, 13 Feb 2012 19:50:53 +0100	[thread overview]
Message-ID: <20120213195053.0db35dd9@little-poseidon> (raw)
In-Reply-To: <jhaq04$pev$1@ultimate100.geggus.net>


> > What's your suggestion to improve/secure my configuration?
> 
> I already told you that you need a backport of the latest version of
> libtirpc. The Version included in squeeze is broken.

You recommended to use backports. As you now say the lib is broken
things are different and I finally solved my problem.

For those who face similar issues I sum up my last steps:

- include squeeze-backports and upgrade nfs-common, nfs-kernel-server
  to version 1.2.4 and Linux kernel to 3.2
- replace portmap by rpcbind
- install version 0.2.2 of libtirpc from unstable (forced new libc6)
- remove pseudo root from /etc/exports
- use AES keys for Kerberos

Thanks to all for your helpful hints! :)

regards
  knut


------

# dpkg -l ...
ii  libnfsidmap2                                0.23-2                                      An nfs idmapping library
ii  nfs-common                                  1:1.2.4-1~bpo60+1                           NFS support files common to client and server
ii  nfs-kernel-server                           1:1.2.4-1~bpo60+1                           support for NFS kernel server

ii  libgssrpc4                                  1.8.3+dfsg-4squeeze5                        MIT Kerberos runtime libraries - GSS enabled ONCRPC
ii  librpcsecgss3                               0.19-2                                      allows secure rpc communication using the rpcsec_gss protocol
ii  libtirpc1                                   0.2.2-5                                     transport-independent RPC library
ii  rpcbind                                     0.2.0-4.1                                   converts RPC program numbers into universal addresses

ii  linux-image-3.2.0-0.bpo.1-686-pae           3.2.4-1~bpo60+1                             Linux 3.2 for modern PCs

  reply	other threads:[~2012-02-13 18:50 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
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 [this message]
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=20120213195053.0db35dd9@little-poseidon \
    --to=whats_up@gmx.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lists@fuchsschwanzdomain.de \
    /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