Skip Menu |
 

From: tlyu@mit.edu
Subject: git commit

Let SPNEGO display mechanism errors

To avoid potential recursion we use a thread local variable that tells
us whether the ancestor was called via spnego_gss_display_name(). If
we detect recursion, we assume that we returned a com_err code like
ENOMEM and call error_message(); in the worst case that will result in
an "Unknown error" message.

[ghudson@mit.edu: Edited comments and commit message; removed an
unneeded line of code.]

(cherry picked from commit d160bc733a3dbeb6d84f4e175234ff18738d9f66)

https://github.com/krb5/krb5/commit/60ced93e5350fa6a18f19316e4753f9ebbd8bc9d
Author: Simo Sorce <simo@redhat.com>
Committer: Tom Yu <tlyu@mit.edu>
Commit: 60ced93e5350fa6a18f19316e4753f9ebbd8bc9d
Branch: krb5-1.11
src/include/k5-thread.h | 1 +
src/lib/gssapi/spnego/spnego_mech.c | 42 ++++++++++++++++++++++++++++------
2 files changed, 35 insertions(+), 8 deletions(-)
From: tlyu@mit.edu
Subject: git commit

Test SPNEGO error message in t_s4u.py

Now that #7045 is fixed, we can check for the correct error message
from t_s4u2proxy_krb5 with --spnego.

(back ported from commit 4faca53e3a8ee213d43da8998f6889e7bfd36248)

https://github.com/krb5/krb5/commit/544965cad68a5f0acdcb44634f82e52b470b3755
Author: Tom Yu <tlyu@mit.edu>
Commit: 544965cad68a5f0acdcb44634f82e52b470b3755
Branch: krb5-1.11
src/tests/gssapi/t_s4u.py | 11 +++++------
1 files changed, 5 insertions(+), 6 deletions(-)