Date: Sun, 24 Dec 2023 23:22:32 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275905] nfs client: mount becomes unresponsive Message-ID: <bug-275905-3630-iq6XjIrX24@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275905-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-275905-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275905 --- Comment #6 from Rick Macklem <rmacklem@FreeBSD.org> --- Not exactly. sec=3Dkrb5 says that a RPCSEC_GSS (think Kerberos) session is used to identify the user for all RPCs. The difference w.r.t. krb5p is t= hat it does not encrypt the NFS payload. I doubt it will make any difference, but it sounds like you'll know soon enough. I now have a hunch w.r.t. what might be broken, but I need to look at the c= ode (and if my hunch seems correct) and maybe come up with a patch. You could try the "syskrb5" mount option, which avoids use of the keytab and allows "system operations that maintain the state" to use AUTH_SYS, while t= he rest (all involving file data) use Kerberos. (If my hunch is correct, this will not fix the problem, but might cause it to behave better.) rick ps: I accidentally did this as an email reply... --=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-275905-3630-iq6XjIrX24>