Date: Sat, 07 Jan 2023 23:12:16 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 268823] Kerberized NFS mount with "gssname" option does not work Message-ID: <bug-268823-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268823 Bug ID: 268823 Summary: Kerberized NFS mount with "gssname" option does not work Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: rmacklem@FreeBSD.org Created attachment 239339 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239339&action= =3Dedit replace desired_name with GSS_C_NO_NAME so gss_acquire_cred() works If you attempt a Kerberized NFS mount with the gssname option such as: # mount -t nfs -o nfsv4,sec=3Dkrb5,gssname=3Dhost nfs-server:/ /mnt the gssd daemon gets stuck in the gss_acquire_cred() library call for several seconds. It then returns success, but the credentials are bogus. A workaround is: # kinit -k host/nfs-client.domain # mount -t nfs -o nfsv4,sec=3Dkrb5 nfs-server:/ /mnt The one line patch in the atttachment seems to fix the problem. I have no idea how long this bug has existed, but I suspect it has been broken for quite a while, due to some change in the Heimdal GSSAPI library. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268823-227>