Date: Mon, 02 Nov 2015 01:28:18 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 204185] security/py-kerberos: Update to 1.2.2 Message-ID: <bug-204185-21822-RI4oWxy3J8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204185-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-204185-21822@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=204185 --- Comment #6 from John W. O'Brien <john@saltant.com> --- Something changed from 1.1.1 to 1.2.2 to break (at least) the following. % pkg info -x kerberos py27-kerberos-1.1.1_1 % sudo python -c " import kerberos result, ctx = kerberos.authGSSServerInit('HTTP') print(result==kerberos.AUTH_GSS_COMPLETE) " True vs. % pkg info -x kerberos py27-kerberos-1.2.2 % sudo python -c " import kerberos result, ctx = kerberos.authGSSServerInit('HTTP') print(result==kerberos.AUTH_GSS_COMPLETE) " Traceback (most recent call last): File "<string>", line 3, in <module> kerberos.GSSError: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('No Kerberos credentials available', -1765328243)) I've done a little bit of digging, and I suspect a change to the way that kerberosgss.c:authenticate_gss_server_init() calls gss_acquire_cred(), but I don't yet have proof. The point is that we may wish to defer this update. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204185-21822-RI4oWxy3J8>