[openssl-dev] Is a "no next protocol negotiation" (no-npn) a supported option?

Jeffrey Walton noloader at gmail.com
Mon Mar 21 08:42:00 UTC 2016


On Mon, Mar 21, 2016 at 4:02 AM, Richard Levitte <levitte at openssl.org> wrote:
> Yes, there is such a configuration option: no-nextprotoneg
>

Thank you very much. That leads to:

gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_THREADS
-DOPENSSL_NO_DYNAMIC_ENGINE -DOPENSSL_PIC -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM
-DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM
-DOPENSSLDIR="\"/usr/local/ssl\""
-DENGINESDIR="\"/usr/local/lib64/engines\"" -Wall -O3 -pthread -m64
-DL_ENDIAN  -Wa,--noexecstack -fPIC -Iinclude -I. -MMD -MF
ssl/t1_ext.d.tmp -MT ssl/t1_ext.o -c -o ssl/t1_ext.o ssl/t1_ext.c
ssl/t1_ext.c: In function ‘SSL_extension_supported’:
ssl/t1_ext.c:303:10: error: ‘TLSEXT_TYPE_next_proto_neg’ undeclared
(first use in this function)
     case TLSEXT_TYPE_next_proto_neg:
          ^
ssl/t1_ext.c:303:10: note: each undeclared identifier is reported only
once for each function it appears in
Makefile:5954: recipe for target 'ssl/t1_ext.o' failed


More information about the openssl-dev mailing list