Comment 3 for bug 572656
Revision history for this message
| J. Bruce Fields (bfields-fieldses) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
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.