summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2013-04-12 16:28:14 -0400
committerGreg Hudson <ghudson@mit.edu>2013-04-13 01:09:36 -0400
commit3a447c5a8c95758501cf5a20c161a2d735a02f6d (patch)
tree6a8cefeb5fa86ac1fce338b44d34fefcf9d670bb
parentcae44d2d014985022a001924dce4a56d12c63818 (diff)
downloadkrb5-3a447c5a8c95758501cf5a20c161a2d735a02f6d.tar.gz
krb5-3a447c5a8c95758501cf5a20c161a2d735a02f6d.tar.xz
krb5-3a447c5a8c95758501cf5a20c161a2d735a02f6d.zip
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
-rw-r--r--src/kdc/fast_util.c1
1 files changed, 1 insertions, 0 deletions
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;