Re: PGP SSL

Sorry for german stuff on this list; mail should go directly to Ralf. __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated

Re: success: mod_ssl 2.1b7 (DSO @ Solaris)

Jan, I thought that mod_frontpage required a patch similar to mod_ssl--Could you please give me a description of how you got this to work. -- thanks, sam From [EMAIL PROTECTED] Tue Nov 3 13:33 EST 1998 From: Jan Wedekind [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: success:

Daily tarfiles of the SNAP directory?

Hi Ralf, Could you, until you can make your source tree available via anon-CVS, build nightly tar.gz-archives of the development snapshot? That way, poor souls that don't have ready access to a Unix box with network connection and rsync (like me ;-) ) would be able to test your current

Re: PGP SSL

Sorry for german stuff on this list; mail should go directly to Ralf. Sorry too, I just replied... Steffen __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List

User Interface bug or fundamental SSL bug?

In communicator-pro-v406-export.x86-unknown-linux2.0-glibc2.tar.gz It seems reasonable to expect that, when accessing a secure server, a session key would be exchanged _before_ any other communication between the server and browser. Superficially, this does _not_ seem to be the case with

ANNOUNCE: mod_ssl 2.1b8 (approaching 2.1.0)

Puhh! Today I've implemented the last "feature" on my 2.1.0 TODO list: The `SSLOptions' directive. This means we are now finally approaching the 2.1.0 version. Because what is now mainly missing is updating the documentation and the README files in the distribution. It's good this way

Building mod_ssl without apache source?

So far mod_ssl can only be built with apache sources. I've tanken a look at mod_php3 and it can be built without the apache sources (just the header files). Is there any way to build mod_ssl as a module without having the apache sources. I think it would be very useful when building RPMs. I

Re: mod_perl again

On Tue, Nov 03, 1998, John Leveron wrote: I know this has been asked before, but for compiling: Apache 1.3.3 mod_ssl mod_ssl-2.0.13 (or 14, now) -1.3.3 mod_perl-1.16 What are the proper compile steps (for a RH 5.1 x86 system)? I seem to (vaguely) remember something about order of

Error with Communicator 4.05 for Linux

My newly installed and running Apache with SSL is finally running and the certificate dialogs and encryption works fine with my old Netscape 3.04 (Linux) browser, BUT not with my Communicator 4.05 (Linux). I get a error dialog with: "The security library has encountered an out of memory

[BugDB] PRIVATE: SSLRequiredCiphers does not work? (PR#40)

Full_Name: Yutaka OIWA Version: 2.0.9- OS: Linux Submission from: 84.pool5.tokyo.att.ne.jp (165.76.22.99) I added SSLRequiredCiphers DEFAULT:!IDEA to the main server section of httpd.conf and SSLEnable to the virtual-host section. However, % ssleay s_client -cipher IDEA can still connect

Re: [BugDB] PRIVATE: SSLRequiredCiphers does not work? (PR#40)

On Wed, Nov 04, 1998, [EMAIL PROTECTED] wrote: I added SSLRequiredCiphers DEFAULT:!IDEA to the main server section of httpd.conf and SSLEnable to the virtual-host section. However, % ssleay s_client -cipher IDEA can still connect to the server with IDEA cipher. I think that the

Re: RfC: SSLVerifyDepth argument

In article you wrote: [...] And the depth check is done via | if (depth = SSLVerifyDepth) error... [...] My opinion is that the depth counting is ok startinbg from 0 and intuitive. But the check should be | if (depth SSLVerifyDepth) error... [...] Votes for the "=" to "" change and to