Hi Steve,
I get that maybe compilation is made problematic to prevent "no-tlsext" to be
used, but what I think is why is it problematic only on Win32 and Win64
systems, compilation with the "no-tlsext" flag is not problematic on an HPUX
system, I was able to build it without any issues.
On a
On Wed, Apr 07, 2010, Kaila, Ashish wrote:
>
> Hi,
>
> I made the following changes in ssl.h (have indicated the changes with a
> comment //added this)
>
> #ifndef OPENSSL_NO_TLSEXT //added this
> /* TLS extensions functions */
> int SSL_set_session_ticket_ext(SSL *s, void *ext_data, int ext_
& Regards
Ashish
-Original Message-
From: Kaila, Ashish
Sent: Wednesday, April 07, 2010 4:12 PM
To: 'openssl-users@openssl.org'
Subject: Problem building OpenSSL version 1.0.0 using no-tlsext flag
Hi,
I took the source of Openssl 1.0.0 and tried building it after running
per
Hi,
I took the source of Openssl 1.0.0 and tried building it after running
perl Configure no-idea no-rc5 no-mdc2 no-md2 no-krb5 no-tlsext VC-WIN32
The build fails with the following link errors.
SSLEAY32.def : error LNK2001: unresolved external symbol
SSL_set_session_secret_cb
SSLEAY32.def : e
