> 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]
> Autom
My apologies for editorializing. I don't do enough work on either to publicly
post in this kind of debate.
Rick Saltzman
> Rick Saltzman wrote:
> >
> > While I don't currently have a production server using ssl in use I build the
> > mod_ssl version from time to time to track its evolution an
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: succ
Hi Ralf,
Yesterday, I tried compiling Apache 1.3.3 and mod_ssl 2.1.7 on
win32, first patching the apache source, then building it without
DSO and finally compiling mod_jserv (which itself is an DSO
module). The bad part is that I get an "illegal read access"
error immediately on startup, the
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 develo
> 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
> BTW: beim patchen kam folgender Fehler:
> Error: Application of SSL patch failed:
> -
> Patching file htdocs/manual/mod/directives.html using Plan A...
> Hunk #1 succeeded at 206.
> done
Hoffe, ich oute mich jetzt nicht als Idiot, aber:
Wo ist da e
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 compilation being important.
Thanks!
Best, Joh
On Tue, Nov 03, 1998, [EMAIL PROTECTED] wrote:
> Yesterday, I tried compiling Apache 1.3.3 and mod_ssl 2.1.7 on
> win32, first patching the apache source, then building it without
> DSO and finally compiling mod_jserv (which itself is an DSO
> module). The bad part is that I get an "illegal read
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
Netscap
Hello Sam,
because you asked on the list, I will answer here too:
(sorry for the inconvenience to other readers)
> 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.
At least I did some more patch
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 be
3-Nov-98 23:54 you wrote:
> 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
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 th
On Tue, Nov 03, 1998, Martin Maciaszek wrote:
> 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).
Yes, I know, because I was the guy who initially implemented this
APXS-based approach
Just for your information:
I've uploaded two more packages to the mod_ssl Contrib area:
o dumpasn1:
This is an excellent tool from Peter Gutmann to dump an arbitrary ASN.1
object file. For instance with this you can dump a X.509 certificate and see
the exact extensions (which neither "ssl
3-Nov-98 09:37 you wrote:
> 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).
Yes, but mod_php3 is HORRIBLE here. Right sample would be mod_perl 1.15 or
1.17 (mod_php3 does not use option
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
On Tue, Nov 03, 1998, [EMAIL PROTECTED] wrote:
> 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 ;-)
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 error.
> On Wed, 4 Nov 1998 15:55:42 +0100, "Ralf S. Engelschall" <[EMAIL PROTECTED]>
>said:
>> What are the proper compile steps (for a RH 5.1 x86 system)? I seem to
>> (vaguely) remember something about order of compilation being important.
ralf> Ops, did you missed the step-by-step list at the
On Wed, Nov 04, 1998, Andreas Järund wrote:
> 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 s
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
I've seen no problem with Communicator 4.04 Linux - or 4.05 Windows -
haven't tried 4.05 Linux.
\/\/ I-I I T
Blauvelt
[EMAIL PROTECTED]
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Su
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 t
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 ">" c
26 matches
Mail list logo
