On Wed, Nov 01, 2000 at 03:58:29PM -0500, Gregory Nicholls wrote:
> <grumble> must be NT's bloody runtime then. If I try to fopen a NULL filename it
>blows up. I changed s_server.c so
> that it only calls load_dh_param() if there's a real file. Guess what. Now it works
>.. . .
That makes sense. When looking into the source, in the case of -nocert,
a NULL pointer is passed to load_dh_param() and this NULL pointer is
passed via BIO_new_file() to fopen(). [As you already analyzed]
The manual page of fopen() does not indicate whether the behaviour of fopen()
is defined for NULL as filename argument, so I guess that the behaviour
of NT does not match the typical behaviour of Linux (or HP-UX), but NT is
not necessarily wrong.
Does anybody know whether fopen(NULL, ...) is allowed at all?
Otherwise s_server should be fixed...
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
