Hi,
I can confirm that the issue still exists with version 1:1.2.3-2.
The workaround with allow_weak_crypto=true also fails to fix this.
If I perform a immediate downgrade to nfs-common 1:1.2.2-5 everything
works fine again if (and only if) allow_weak_crypto=true is present in
the config
Hello,
nfs-common 1:1.2.3-2 from wheezy works flawlessly for me with sec=krb5p and
allow_weak_crypto = true in /etc/krb5.conf.
Regards
Friedemann
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
2 matches
Mail list logo