> > "The security library has encountered an out of memory error. Please
> > try to reconnect."
>
> Sounds like a local browser problem to me I've no clue, sorry.
I know this problem but I forgot our context in which we had it...
1. Try to delete the Site-Cert, restart netscape and try ag
I find right as it is now:
Reason:
Depth = 0 -> disabled
Depth = 1 -> father <-> son
Depth = 2 -> son <-> father <-> son
is like in akin degrees... two brothers are second degree akins
because they share a common ancestor aunt and niece are third degree
and so on...
"Ralf S. Engelschall" wro
> Still no votes from the hacker community?
>
> Seems like no one uses SSLVerifyDepth... ;-)
>
> Please say "this is a bad change, because..." now or
> I'll change it this way for 2.1b9/2.1.0.
I'm sure i don't understand everything about Client Certs. It's
always been one of those things that
> Weird. I'm ready to got such question from dumb Winblows user but from
> Linux user... Unbeliveable :-((
I'm sorry you misunderstood. That was not a question so much as a
rhetorical question, a comment on the Navigator user interface.
> Use mod_ssl logs or such not Netscape lock icon (BTW loc
Ralf, Tom, and others, I've gotten another clue to my non-working web server. As you
may recall, everything seems to have compiled correctly, but hitting my website:
https://mymachine.foo.com:8443/
simply causes Netscape to "spin" endlessly. s_client displays a similar problem,
showi
On Sat, 31 Oct 1998 16:25:34 +0100, you wrote:
>
>We have a PR (#35) where the user is confused by the interpretation of the
>SSLVerifyDepth argument. He wants to only accept a cert which has to be
>directly signed by the to be known CA certificate, i.e. he wants to not allow
>intermediate CA cer
Hello Ralf,
I got the following problems, partly by configuration mistake
(on that other machine, where I did have the problems with another
compiled apache and mod_perl, but no longer have this kind of),
and detected the following:
- If the SSLLog path/directory does not exist, there's no error
On Wed, 4 Nov 1998, James wrote:
> > Weird. I'm ready to got such question from dumb Winblows user but from
> > Linux user... Unbeliveable :-((
>
> I'm sorry you misunderstood. That was not a question so much as a
> rhetorical question, a comment on the Navigator user interface.
>
Oops.
> >
On Thu, Nov 05, 1998, Jan Wedekind wrote:
>[...]
> - If the SSLLog path/directory does not exist, there's no error message
> within the error_log, and the parent dies with exit(1).
>
> I just greped through the source but didn't see the
> error within ssl_log_open(). Maybe the error is detec
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
> 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 r
Hi,
> Ralf, Tom, and others, I've gotten another clue to my non-working web server.
> As you may recall, everything seems to have compiled correctly, but hitting
> my website:
>
> https://mymachine.foo.com:8443/
>
It's the additional port nr. '8443' which confuses mod_ssl.
the same hap
On Thu, Nov 05, 1998, Jan Wedekind wrote:
> > Ralf, Tom, and others, I've gotten another clue to my non-working web server.
> > As you may recall, everything seems to have compiled correctly, but hitting
> > my website:
> >
> > https://mymachine.foo.com:8443/
> >
> It's the additional po
>
> Hmm, at least my problem is solved now. Next is trying to build a mini
> CA and implementing some kind of authorization scheme using
> certificate lookups in an LDAP database like Netscape does.
> The certificate delivers a DN, so with some mapping of components /
> attributes I should be a
> Wait! On _ALL_ my testings on en1.engelschall.com I use port 8080 for HTTP an
> d
> 8443 for HTTPS because en1 also runs the non-testing Apache+mod_ssl on 80/443
> .
Well, now I got the message and may explain the behaviour
(which I tried before)
I (and also the other writer to the list) made
On Thu, Nov 05, 1998, Jan Wedekind wrote:
> > Wait! On _ALL_ my testings on en1.engelschall.com I use port 8080 for HTTP an
> > d
> > 8443 for HTTPS because en1 also runs the non-testing Apache+mod_ssl on 80/443
>
> Well, now I got the message and may explain the behaviour
> (which I tried befor
16 matches
Mail list logo
