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. -- kerberized nfs regression in lucid https://bugs.launchpad.net/bugs/572656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
