> Sometime in the last few months, changes were made to e_os2.h in
> the stable 0.9.8 series, which broke the DJGPP build. It looks
> like a cleanup was made, removing OPENSSL_SYSNAME_WIN16, but the
> OPENSSL_SYSNAME_MSDOS code appears to have been accidentally removed.
> I see that none of the pl
> OPENSSL_Applink can be implemented only in main EXE module.
Yes. Keep in mind that purpose of applink is to facilitate port of Unix
and elder Win32 applications, when working around the Win32-specific
run-time environment problems is like "hell, it was working for
*years*." But for new and e
Hi,
We recently ran Coverity, a static source analysis tool, against OpenSSL
0.9.7 and 0.9.8. We found a number of problems such as the potential to
access null pointers, lack of error checking on return codes, etc.
There are in the neighborhood of 25 errors that we considered worth fixing.
