Re: [openssl.org #2246] dtls1.h includes winsock.h, overriding the #undefs from ossl_typ.h on Windows

2010-04-27 Thread M.-A. Lemburg via RT
Roumen Petrov via RT wrote: M.-A. Lemburg via RT wrote: An application that only includes openssl/ssl.h from OpenSSL 1.0.0 and doesn't use winsock.h will run into problems on Windows, since the dtls1.h header file includes the winsock.h header file long after the ossl_typ.h header file was

Re: [openssl.org #2246] dtls1.h includes winsock.h, overriding the #undefs from ossl_typ.h on Windows

2010-04-27 Thread M.-A. Lemburg
Roumen Petrov via RT wrote: M.-A. Lemburg via RT wrote: An application that only includes openssl/ssl.h from OpenSSL 1.0.0 and doesn't use winsock.h will run into problems on Windows, since the dtls1.h header file includes the winsock.h header file long after the ossl_typ.h header file was

Re: [openssl.org #2245] [PATCH] Add /Zi to VC++ CFLAG in debug configuration (1.0.0 and 0.9.8)

2010-04-27 Thread Mounir IDRASSI via RT
Hi, I have on purpose only added /Zi to the debug build because it is not always desirable to add symboles to release builds whereas it is always needed for debug ones. -- Mounir IDRASSI IDRIX http://www.idrix.fr On 4/26/2010 11:58 PM, William A. Rowe Jr. wrote: On 4/26/2010 1:18 PM, Mounir

Re: [openssl.org #2245] [PATCH] Add /Zi to VC++ CFLAG in debug configuration (1.0.0 and 0.9.8)

2010-04-27 Thread William A. Rowe Jr.
On 4/27/2010 5:35 AM, Mounir IDRASSI wrote: Hi, I have on purpose only added /Zi to the debug build because it is not always desirable to add symboles to release builds whereas it is always needed for debug ones. No, it's always desirable, and actually irresponsible not to track symbols

Re: [openssl.org #2245] [PATCH] Add /Zi to VC++ CFLAG in debug configuration (1.0.0 and 0.9.8)

2010-04-27 Thread William A. Rowe Jr. via RT
On 4/27/2010 5:35 AM, Mounir IDRASSI wrote: Hi, I have on purpose only added /Zi to the debug build because it is not always desirable to add symboles to release builds whereas it is always needed for debug ones. No, it's always desirable, and actually irresponsible not to track symbols

Re: Building Openssl on OpenVMS using extended parse-style

2010-04-27 Thread Steven M. Schweda
For the morbidly curious, I may have a working LIB$INITIALIZE module for OpenSSL, which would cause it to preserve case for its command-line arguments (on modern, non-VAX systems, with SET PROCESS /PARSE_STYLE = EXTENDED). That stuff should be in:

Website error

2010-04-27 Thread William Rowe
http://openssl.org/docs/fips/fipsnotes.html contains a spurious reference to http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1058.pdf, which was supposed to link to 140sp1051.pdf.

Re: Website error

2010-04-27 Thread Dr. Stephen Henson
On Tue, Apr 27, 2010, William Rowe wrote: http://openssl.org/docs/fips/fipsnotes.html contains a spurious reference to http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1058.pdf, which was supposed to link to 140sp1051.pdf. Thanks for reporting that. Fixed now. Steve. --