Hi,
I've created a secure Apache server using mod_ssl and it works fine. But as
I tried to click lots of links in a secure environment while pages are
still received I sometimes get the message that there was an insecure item
in the page, so Internet Explorer switches to non-secure mode. The serv
Full_Name: Edward Heal
Version: 2.0.11
OS: Solaris 2.5.1
Submission from: niss.ucs.ed.ac.uk (129.215.200.105)
In my setup, I am not interested in logging SSL connections, so
I used the directive
SSLLog /dev/null
This causes the server to terminate with segmentation violation.
_
Hi,
I have a question regarding the following situation.
In the US, using strong cryptography is regulated. However, there are
certain situations under which you can use strong cryptography and the
export licenses are approved on the per case basis. I know the base
Apache package does not have S
> glin wrote:
> When I run the configure.bat from command line, it appears OK. Bu the source
> files are not patched. Rej files were produced. If I run the patch from
> command line directly, the output says "x of x hunks failed". Any suggestins
> that I can try to figure out what I did was in
Ok, RSE is back in town from ApacheCon'98. I'm totally flooded with mails, so
it needs at least one more day until you see replies from me, especially on
the mailing list. So, when you expect a reply just wait a little bit more,
please. Nothing gets lost, I try to answer all questions. I just n
Estarei participando de um congresso nos dias 16 e17 de outubro. Devo
retornar somente na terca-feira-feira dia 20/10/98. Se sua mensagem necessitar de
atendimento urgente, por favor utilize o endereco
[EMAIL PROTECTED]
Luiz Cunha
Yes. The beta version are suposed to work on NT. I found the problem was
in the pathing program. I found another port of GNU patch (2.1) and it
worked. Now I have it build on NT 4.0 (apache 1.3.3 and mod_ssl 2.1b6)
with a few warning messages. I don't know how serious these warning are.
But I
I don't think you can. The law doesn't care where it come from. Once is
made here, goes abroad means export. I am not a lawyer, but thats what I
heard. Easily accessible and export are separate things. Before you
export, ask the commerce department (or your lawyer).
On Thu, 15 Oct 1998, Pete
In article <> you wrote:
> Yes. The beta version are suposed to work on NT. I found the problem was
> in the pathing program. I found another port of GNU patch (2.1) and it
> worked. Now I have it build on NT 4.0 (apache 1.3.3 and mod_ssl 2.1b6)
> with a few warning messages. I don't know h
In article <> you wrote:
> Data Base Updated
> CA verifying: server.crt <-> CA cert
> server.crt: /C=UK/ST=Scotland/L=Edinburgh/O=MIDS
> Europe/OU=Sysadmin/CN=John [EMAIL PROTECTED]
> error 7 at 0 depth lookup:certificate signature failure
Ok, as already said, first the CN is wrong. Use "www.yo
> > When building Apache 1.3.3 after incorporating mod_ssl,
> > I get the following message when compiling "mod_ssl.c"
> > (message wrapped for readability):
> >
> > cc -c -I../../os/unix -I../../include -DAIX=42 -U__STR__
> > -DAIX_BIND_PROCESSOR -qnogenpcomp -qnousepcomp -DMOD_SSL=200113
>
Hello Edward,
> In my setup, I am not interested in logging SSL connections, so
> I used the directive
>
> SSLLog /dev/null
>
This should be the default (as with other Log-directives within apache),
so just omit the SSLLog configuration command or place a '#' before it.
Jan
Hello Edward,
> In my setup, I am not interested in logging SSL connections, so
> I used the directive
>
> SSLLog /dev/null
>
This should be the default (as with other Log-directives within apache),
so just omit the SSLLog configuration command or place a '#' before it.
Jan
___
> In article <> you wrote:
>
> > Yes. The beta version are suposed to work on NT. I found the problem
was
> > in the pathing program. I found another port of GNU patch (2.1) and it
> > worked. Now I have it build on NT 4.0 (apache 1.3.3 and mod_ssl 2.1b6)
> > with a few warning messages.
On Tue, 20 Oct 1998 13:43:04 GMT,
Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
> In article <> you wrote:
>
> > Yes. The beta version are suposed to work on NT. I found the problem was
> > in the pathing program. I found another port of GNU patch (2.1) and it
> > worked. Now I have it bu
In article <> you wrote:
> No important information/questions in this message,
> just wanted to tell that these days I finally switched from
> apache_1.3.1+ben-ssl_1.19 to apache_1.3.3+mod_ssl_2.1.13.
> Despite I have a few custom modules and patches here, building
> of the server was amazingly
In article <> you wrote:
> Hi. I just tried to build the latest 2.0 version of mod_ssl. It complained
> about not finding the header gnu/stubs.h. The system is a Linux libc5 slackware
> box. on my libc6 box, this header exists. So the question is, does mod_ssl on
> Linux require libc6, or i
In article <> you wrote:
> i've installed SSLeay-0.9.0b and mod_ssl-2.0.13-1.3.3
> with Apache on a SuSE Linux machine. Now i'm trying to set up a closed user
> group via SSL. I've set up my own CA and issued some client certificates
> for my users. Everything works fine so far except when peopl
In article <> you wrote:
> I've created a secure Apache server using mod_ssl and it works fine. But as
> I tried to click lots of links in a secure environment while pages are
> still received I sometimes get the message that there was an insecure item
> in the page, so Internet Explorer switche
First, thanks to all who attended the mod_ssl presentation at ApacheCon'98.
There were really a lot of people in Imperial Ballroom A (see the tiny picture
at the right) and the positive feedback the days after it was impressive.
Thanks.
For those who couldn't attend ApacheCon'98 but are still in
In article <> you wrote:
> Full_Name: Frank-Christian Kruegel
> Version: 2.0.13-1.3.3
> OS: SunOS 4.1.3_U1
> Submission from: bruker2.bfa.de (194.77.113.195)
> following setup:
> - apache 1.3.3
> - php 3.0.5
> - mod_auth_mysql 2.20
> - mod-ssl-2.0.13-1.3.3
> build works under solaris 2.6 (gcc
Oops, that fscking mailer garbled the patch again
> In article <> you wrote:
>
> > Yes. The beta version are suposed to work on NT. I found the problem was
> > in the pathing program. I found another port of GNU patch (2.1) and it
> > worked. Now I have it build on NT 4.0 (apache 1.3.3 a
Hi,
After having success with my fresh "Apache/1.3.3 (Win32) mod_ssl/2.1b6
SSLeay/0.9.0b",
I tried to connect to the webserver with client certificates enabled,
but get
only a "Certificate Chain too long" in the error logfile. I'm using the
Snake Oil
Certificate on the server and a Thawte Freema
On Tue, Oct 20, 1998, [EMAIL PROTECTED] wrote:
> After having success with my fresh "Apache/1.3.3 (Win32) mod_ssl/2.1b6
> SSLeay/0.9.0b",
> I tried to connect to the webserver with client certificates enabled,
> but get
> only a "Certificate Chain too long" in the error logfile. I'm using the
> S
Full_Name: Marinus Damm
Version: 2.0.13
OS: Linux
Submission from: blv-proxy-05.boeing.com (12.13.226.15)
httpd.conf has:
SSLEnable
SSLRequireSSL
SSLCACertificateFile/usr/local/apache/etc/ssl.crt/ca-cert.crt
SSLVerifyClient require
SSLVerifyDepth 2
25 matches
Mail list logo
