From 8ed92460b7a4a2a310f1b0dde6e36f9055f5b87b Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Tue, 21 Mar 2017 16:12:37 +0000 Subject: [PATCH] Fix BAD CCS alert in DTLS Set the correct variable, and then actually send the alert! Found by, and fix suggested by, Raja Ashok. Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/3009) --- ssl/d1_pkt.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ssl/d1_pkt.c b/ssl/d1_pkt.c index 7a02459f2b..10586fee54 100644 --- a/ssl/d1_pkt.c +++ b/ssl/d1_pkt.c @@ -1323,9 +1323,9 @@ int dtls1_read_bytes(SSL *s, int type, unsigned char *buf, int len, int peek) /* XDTLS: check that epoch is consistent */ if ((rr->length != ccs_hdr_len) || (rr->off != 0) || (rr->data[0] != SSL3_MT_CCS)) { - i = SSL_AD_ILLEGAL_PARAMETER; + al = SSL_AD_ILLEGAL_PARAMETER; SSLerr(SSL_F_DTLS1_READ_BYTES, SSL_R_BAD_CHANGE_CIPHER_SPEC); - goto err; + goto f_err; } rr->length = 0; -- 2.25.1