From 3a447c5a8c95758501cf5a20c161a2d735a02f6d Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Fri, 12 Apr 2013 16:28:14 -0400 Subject: Set msg_type when decoding FAST requests An RFC 6113 KrbFastReq contains a padata sequence and a KDC-REQ-BODY, neither of which contain the msg-type field found in a KDC-REQ. So when we decode the FAST request, the resulting krb5_kdc_req structure has a msg_type of 0. Copy msg_type from the outer body, since we make use of it in further KDC processing. ticket: 7605 (new) target_version: 1.11.3 tags: pullup --- src/kdc/fast_util.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/kdc/fast_util.c b/src/kdc/fast_util.c index 40c5783035..4fa36c6fc2 100644 --- a/src/kdc/fast_util.c +++ b/src/kdc/fast_util.c @@ -239,6 +239,7 @@ kdc_find_fast(krb5_kdc_req **requestptr, KRB5_PADATA_FX_COOKIE); if (retval == 0) { state->fast_options = fast_req->fast_options; + fast_req->req_body->msg_type = request->msg_type; krb5_free_kdc_req( kdc_context, request); *requestptr = fast_req->req_body; fast_req->req_body = NULL; -- cgit