OT: OpenSSL 1.0.1f

[Aidan Scheller]

Does using the --with-openssl-opt="enable-ec_nistp_64_gcc_128"
 configure parameter without the *--with-openssl *cause a static version of
OpenSSL to be created for Nginx?  I'm unsure as the configuration summary
then lists that the system library is being used.

Thanks,

Aidan



On Wed, Jan 8, 2014 at 4:08 AM, itpp2012 <nginx-forum at nginx.us> wrote:

> itpp2012 Wrote:
> -------------------------------------------------------
> > 1.0.1f against 1.5.9 mainline (today);
> >
> > .\ssl\s23_clnt.c(286) : warning C4244: 'initializing' : conversion
> > from 'time_t' to 'unsigned long', possible loss of data
>
> Also found by http://rt.openssl.org/Ticket/Display.html?id=3220
> and fixed in .\ssl\s23_clnt.c(line 286):
>
> [...]
> int ssl_fill_hello_random(SSL *s, int server, unsigned char *result, int
> len)
> [...]
>         if (send_time)
>                 {
> //        unsigned long Time = time(NULL);
>         unsigned long Time = (unsigned long)time(NULL);
>         unsigned char *p = result;
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,246071,246128#msg-246128
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140108/3f8a2126/attachment.html>