Initialize next_proto in s_server - resolves incorrect attempts to free
authorScott Deboy <sdeboy@secondstryke.com>
Thu, 12 Sep 2013 00:22:00 +0000 (17:22 -0700)
committerAdam Langley <agl@chromium.org>
Fri, 13 Sep 2013 15:31:39 +0000 (11:31 -0400)
Cherry pick of b0d27cb9028cbf552612baa42255737cca0e32d2.

apps/s_server.c

index 8a5a1376c0bf7ff8345cbe15065df0f1d04f58b4..9a22345c2174a81e494910aba119c638f5d315fb 100644 (file)
@@ -1023,7 +1023,7 @@ int MAIN(int argc, char *argv[])
         tlsextctx tlsextcbp = {NULL, NULL, SSL_TLSEXT_ERR_ALERT_WARNING};
 # ifndef OPENSSL_NO_NEXTPROTONEG
        const char *next_proto_neg_in = NULL;
-       tlsextnextprotoctx next_proto;
+       tlsextnextprotoctx next_proto = { NULL, 0};
        const char *alpn_in = NULL;
        tlsextalpnctx alpn_ctx = { NULL, 0};
 # endif