linux-kernel - Re: NFS4 sec=krb5 broken in 3.9-rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130426171640.GF17268@fieldses.org>
Date:	Fri, 26 Apr 2013 13:16:40 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Malte Schröder <maltesch@....de>
Cc:	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: NFS4 sec=krb5 broken in 3.9-rc8

On Fri, Apr 26, 2013 at 06:56:19PM +0200, Malte Schröder wrote:
> On 26.04.2013 17:23, J. Bruce Fields wrote:
> > On Fri, Apr 26, 2013 at 11:20:39AM +0200, Malte Schröder wrote:
> >> On 24.04.2013 21:23, J. Bruce Fields wrote:
> >>> On Wed, Apr 24, 2013 at 07:07:59PM +0200, Malte Schröder wrote:
> >>> Probably some of those "svc_process dropit"s are coming from attempts to
> >>> look up the newly created cred (so lookups in the rsc_cache) which fail
> >>> for some reason.  I'm not sure what that would be.
> >>>
> >>> --b.
> >>
> >> Hi,
> >> I tried bisecting the problem. It identified
> >> 683428fae8c73d7d7da0fa2e0b6beb4d8df4e808 as the problem, reverting it
> >> didn't fix the problem, though. During the process there where some
> >> states where mounting wouldn't hang but be denied. I will try bisecting
> >> again, later.
> > 
> > Oh, so probably 3c34ae11fac3b30629581d0bfaf80f58e82cfbfb "nfsd: fix krb5
> > handling of anonymous principals" needs backporting to stable--could you
> > confirm whether applying that helps?
> > 
> > Thanks for the bisection.
> > 
> > --b.
> > 
> 
> Well, I have the problem on 3.9-rc8, 3.8.5 works totally fine for me.

Oops, right--should have looked at the subject line.

> Just for fun I reverted the path you mentioned, and now the behaviour
> has changed: It doesn't hang anymore, now I get access denied from the
> server.

OK, I'm out of ideas for now....

--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/