From 534523d9751333936c4698628a7545f16b40d0c3 Mon Sep 17 00:00:00 2001 From: rmacklem Date: Thu, 25 Oct 2012 19:30:58 +0000 Subject: Modify the comment to take out the names and URL. Requested by: kib MFC after: 3 days --- sys/rpc/rpcsec_gss/svc_rpcsec_gss.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) (limited to 'sys/rpc') diff --git a/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c b/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c index 0437189..64e691e 100644 --- a/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c +++ b/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c @@ -1025,12 +1025,9 @@ svc_rpc_gss_validate(struct svc_rpc_gss_client *client, struct rpc_msg *msg, rpc_gss_log_status("gss_verify_mic", client->cl_mech, maj_stat, min_stat); /* - * Attila Bogar and Herbert Poeckl reported similar problems - * w.r.t. a Linux NFS client doing a krb5 NFS mount against the - * FreeBSD server. We determined this was a Linux bug: - * http://www.spinics.net/lists/linux-nfs/msg32466.html, where - * the mount failed to work because a Destroy operation with a - * bogus encrypted checksum destroyed the authenticator handle. + * A bug in some versions of the Linux client generates a + * Destroy operation with a bogus encrypted checksum. Deleting + * the credential handle for that case causes the mount to fail. * Since the checksum is bogus (gss_verify_mic() failed), it * doesn't make sense to destroy the handle and not doing so * fixes the Linux mount. -- cgit v1.1