In order to understand the source of GSS_S_FAILURE one needs to know
GSS minor status code which could be translated only to text by GSS-API
gss_display_status(), and knowing the text wouldn't change the returned
error code anyway. A curious one (a developer) would need to generate
a +kerberos log.
Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru>
---
dlls/kerberos/krb5_ap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dlls/kerberos/krb5_ap.c b/dlls/kerberos/krb5_ap.c
index …
[View More]d40ec04dd5..0ff6ae2738 100644
--- a/dlls/kerberos/krb5_ap.c
+++ b/dlls/kerberos/krb5_ap.c
@@ -710,6 +710,7 @@ static NTSTATUS status_gss_to_sspi( OM_uint32 status )
case GSS_S_OLD_TOKEN: return SEC_E_INVALID_TOKEN;
case GSS_S_UNSEQ_TOKEN: return SEC_E_OUT_OF_SEQUENCE;
case GSS_S_GAP_TOKEN: return SEC_E_OUT_OF_SEQUENCE;
+ case GSS_S_FAILURE: return SEC_E_INTERNAL_ERROR;
default:
FIXME( "couldn't convert status 0x%08x to NTSTATUS\n", status );
--
2.16.3
[View Less]