kerberized nfs regression in lucid

Bug #572656 reported by J. Bruce Fields
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

In karmic, kerberos NFS mounts worked. After an upgrading my nfs client to lucid this morning (kerberos server, nfs server, keytab all unchanged), a mount now gets "mount.nfs4: access denied by server while mounting troy:/vol/home".

Logs show "rpc.gssd[4305]: ERROR: No credentials found for connection to server troy.citi.umich.edu"

Examination of wireshark trace shows a KRB5KDC_ERR_PREAUTH_REQUIRED response to the kerberos AS-REQ.

Revision history for this message
J. Bruce Fields (bfields-fieldses) wrote :
Revision history for this message
Don (julien-garet) wrote :

Hello, I have just discovered that it might be related to : https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/512110

It solved my problem.

Revision history for this message
J. Bruce Fields (bfields-fieldses) wrote :

Doh. I should have known about that--yes, adding "allow_weak_crypto = true" to the [libdefaults] section of my client's krb5.conf file allows the mount to succeed.

I'm not sure what the correct solution is--ideal might be to backport the new nfs/krb5 patches queued for the 2.6.35 kernel (and the corresponding nfs-utils patches) and to keep allowing weak crypto until that's done.

I don't know if that's practical.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.