My apologies if this makes it onto the list twice - some mail problems earlier left me unsure whether or not this got posted or not. Thanks to Ralf and Tim Hudson for helping in my continuing problems getting mod_ssl to work on my Alpha running Digital Unix 4.0d. To recap, everything seems to compile just fine, and once the server is started, files are served by Apache using HTTP just fine, but any attempt to retrieve a file with "https://" (using Netscape or SSLeay's s_client) simply causes the client to hang (Netscape), or in s_client's case, to display the first four lines of the Snake Oil certificate, then hang. Today I tried going back and recompiling everything from scratch, with one exception: this time, I did not include the rsaref-2.0 library into SSLeay. And THIS time, it appeared to work. (or at least I THINK it worked. Netscape 4.05 told me "This certificate is not valid for this application", or something like that, but Netscape 3.x and MSIE 4.x allowed me to access the https:// URL, albeit with lots of warnings about the phony Snake Oil Certificate. So I suppose that means it worked.) So can anyone tell me why the rsaref-2.0 library would be causing this trouble? It compiled without any warnings, and SSLeay compiles with it without a hitch - the problems don't come till later. And I assume that as a US resident I'm legally required to use rsaref-2.0? Is there anything else I can do now? Any way to further track down this problem? Thanks again to anyone who can help. -----== Sent via Deja News, The Discussion Network ==----- http://www.dejanews.com/ Easy access to 50,000+ discussion forums ______________________________________________________________________ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
