Re: [BugDB] RAND_MAX missing on SunOS (PR#110)
On Mon, Feb 22, 1999, [EMAIL PROTECTED] wrote: Full_Name: Dominic J. Hulewicz Version: 2.2.3-1.3.4 OS: SunOS 4.1.4 Submission from: gate.sevenww.net (193.130.32.145) Apache/mod_ssl would not compile on SunOS as the RAND_MAX constant is missing. I fixed pkg.sslmod/ssl_engine_rand.c as follows: # diff ssl_engine_rand.c.orig ssl_engine_rand.c 175a176,180 #ifndef RAND_MAX #include limits.h #define RAND_MAX INT_MAX #endif Oh yes, although RAND_MAX is POSIX, SunOS isn't. Fixed as suggested by you. Thanks for the patch. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Problems with Apache 1.3.4 + mod_ssl 2.2.3
Hello all, I have very strange problem with mod_ssl 2.2.3. As with 2.1.8. I installed mod_ssl, configured apache. I used Thawte signed certs. And I have very strange problem... When I try to get file which is less than 1k all is ok. When I try to get file which is 8k length, I get following error: GET / HTTP/1.1 Host: www.myhost.com SSL3 alert write:fatal:unknown 16956:error:1408F109:SSL routines:SSL3_GET_RECORD:wrong version number:s3_pkt.c:276: SSL3 alert write:warning:close notify I used s_client to test. Sincerely Yours, Denis Y. Pershin -- E-Mail: [EMAIL PROTECTED] HomePage: http://www.software.ru/dyp/ FidoNet: 2:5000/120.5 -- __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Verisign rejects CSR
I have just installed Apache 1.3.4 + mod_ssl 2.2.2 (with openssl 0.9.1c). When trying to submit a CSR to Verisign for a test certificate, I get " Error - Certificate Signing Request The certificate signing request (CSR) you submitted is not signed correctly. Please contact your software vendor. " I have generated two CSRs, one using the mod_ssl faq, and one using the exact instructions from Verisign. The results are the same. Testing the CSR with 'ssleay req -noout -text -in server.csr' looks fine. Any idea what is causing this? Regards, Tore Green [EMAIL PROTECTED] __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Un-Suscribe
unsuscribe __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
