Blame SOURCES/Fix-KCM-client-time-offset-propagation.patch

92593c
From 7e4576cc62a16fa77030c42dcc43c61cdfa5b4e6 Mon Sep 17 00:00:00 2001
92593c
From: Robbie Harwood <rharwood@redhat.com>
92593c
Date: Wed, 14 Aug 2019 13:52:27 -0400
92593c
Subject: [PATCH] Fix KCM client time offset propagation
92593c
92593c
An inverted status check in get_kdc_offset() would cause querying the
92593c
offset time from the ccache to always fail (silently) on KCM.  Fix the
92593c
status check so that KCM can properly handle desync.
92593c
92593c
ticket: 8826 (new)
92593c
tags: pullup
92593c
target_version: 1.17-next
92593c
target_verison: 1.16-next
92593c
92593c
(cherry picked from commit 323abb6d1ebe5469d6c2167c29aa5d696d099b90)
92593c
(cherry picked from commit 7e81b8077cf2cf186dadb96b064573f7c221fbf3)
92593c
---
92593c
 src/lib/krb5/ccache/cc_kcm.c | 2 +-
92593c
 1 file changed, 1 insertion(+), 1 deletion(-)
92593c
92593c
diff --git a/src/lib/krb5/ccache/cc_kcm.c b/src/lib/krb5/ccache/cc_kcm.c
92593c
index 092ab7daf..fe93ca3dc 100644
92593c
--- a/src/lib/krb5/ccache/cc_kcm.c
92593c
+++ b/src/lib/krb5/ccache/cc_kcm.c
92593c
@@ -583,7 +583,7 @@ get_kdc_offset(krb5_context context, krb5_ccache cache)
92593c
     if (cache_call(context, cache, &req, FALSE) != 0)
92593c
         goto cleanup;
92593c
     time_offset = k5_input_get_uint32_be(&req.reply);
92593c
-    if (!req.reply.status)
92593c
+    if (req.reply.status)
92593c
         goto cleanup;
92593c
     context->os_context.time_offset = time_offset;
92593c
     context->os_context.usec_offset = 0;