oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

kdc: use memset rather than {0} to initialize fxreq

Browse Source
This commit is contained in:
Luke Howard
2022-01-17 10:01:26 +11:00
parent 7fb4698aa3
commit 0a59cbca51
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
kdc/fast.c
View File

@@ -459,7 +459,7 @@ fast_unwrap_request(astgs_request_t r,
krb5_principal armor_server_principal = NULL; krb5_principal armor_server_principal = NULL;
char *armor_client_principal_name = NULL; char *armor_client_principal_name = NULL;
char *armor_server_principal_name = NULL; char *armor_server_principal_name = NULL;
PA_FX_FAST_REQUEST fxreq = {0}; PA_FX_FAST_REQUEST fxreq;
krb5_auth_context ac = NULL; krb5_auth_context ac = NULL;
krb5_ticket *ticket = NULL; krb5_ticket *ticket = NULL;
krb5_flags ap_req_options; krb5_flags ap_req_options;
@@ -474,6 +474,7 @@ fast_unwrap_request(astgs_request_t r,
size_t len; size_t len;
int i = 0; int i = 0;
memset(&fxreq, 0, sizeof(fxreq));
memset(&fastreq, 0, sizeof(fastreq)); memset(&fastreq, 0, sizeof(fastreq));
pa = _kdc_find_padata(&r->req, &i, KRB5_PADATA_FX_FAST); pa = _kdc_find_padata(&r->req, &i, KRB5_PADATA_FX_FAST);