On Thu, 12 Sep 2002, Jeremy, Leonard wrote:
> I have setup an apache ssl reverse proxy using v1.3.26 with mod_ssl This
> works but serves a certificate from the reverse proxy to the client instead
> of passing through the certificate from the end server.
Yes of course... it does that by design.
I posted the following question with comp.infosystems.www.servers.unix but
have received no suggestions.
Do you have a solution?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, 9 September 2002 9:34 AM
To: Jeremy, Leonard
Subject: apache reverse proxy
Problem was my CA cert file ( incorrect setting )
(it's the little things)
- Original Message -
From: "Ron Gedye" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 4:15 PM
Subject: [Openca-Users] Fw: SSLVerifyClient statements causing problems?
> Figur
Typo in my email, ( modified from actual syntax) should read:
SSLRequire( %{SSL_CLIENT_S_DN_O} eq "MyOrg" )
- Original Message -
From: "Roberto Hoyle" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 2:50 PM
Subject: Re: SSLVerifyClient statements causin
Ron Gedye wrote:
[snip]
>
> SSLVerifyClientrequire
> SSLVerifyDepth1
> SSLOptions +FakeBasicAuth
> SSLRequire( %{SSL_CLIENT_S_DN_O} eq "MyOrg"
>
>
>
> I have my SSLCACertificatePath & File set as well as the SSLCARevocation...
> (Self signed CA via OpenCA 0.9.1 RC4)
>
>
Hello List
I searched the archives and saw a few mentions of the error that I am
seeing, but no solid solutions so here goes...
In attempting to use client certificates to provide/restrict access to
certain portions of my website I am encountering problems.
Apache 1.3.26, mod_ssl 2.8.10, O
Raj,
Shouldn't your apache statement read apache
-k -D SSL ? Note the space behind the -D. Also I didn't see your attachments
most likely due to it being stripped on the listserv, but you might also want to
check that listen 443 is
in the httpd.conf file.
Regards,
Paul
-Origin
Hi,
I have installed Apache 2.0.39 from source with --enable-so on solaris 8.
Apache works great on default port 80, then I tried to configure it to
work with https on port 443, the server doesn't respond for https. I used
openssl to create csr and certificate. Also, I am attaching both my
Is this a required modules to restrict certain sites/dir's access via
certificates. (apache 1.3.26)
I having trouble with SSLRequireSSL statements as presented on apache's howto
pages, (newby related I'm sure) I have not compiled this modules in nor am
I using it as a DHAVE object. Wonderin
- Original Message -
From: "Sonu Kishore" <[EMAIL PROTECTED]>
>
> it is possible that user "A" logs on to my web site with his user id/
password
> but uses user "B" certificate... in such a case non-repudiation becomes
> ill-logical.
==
Try to use mod_authz_ldap http:/
Hi Peter,
The IP adressess all work fine. Is there a command
that shuts out SSL for normal virtual hosts?
I tried putting "SSLEngine off" in the normal host
container but https://normalhost still shows.
--- Peter Viertel <[EMAIL PROTECTED]>
wrote: > I notice that your virtual hosts are all
usi
i search php4apache-eapi.dll for php version 4.2.3 !
__
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager
Try at php4win.com (by the way if you had done a search for that file
using a search engine like google.com, you would have found it
yourself)
Cheers
Jose
-Original Message-
From: Frédéric [mailto:[EMAIL PROTECTED]]
Sent: 11 September 2002 13:39
To: [EMAIL PROTECTED]
Subject:
Hi,
ho
Hi,
how find the file "php4apache-eapi.dll" for use with apache-mod_ssl
1.3.26 ??
Thanks
__
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Hi,
> "STEP 3: Generating X.509 certificate signed by Snake Oil CA
> [server.crt]
> Certificate Version (1 or 3) [3]:
> Signature ok
> subject=/O=telkom/OU=users/CN=Jose
> Getting CA Private Key
> Verify: matching certificate & key modulus
> read RSA key
> Verify: matching certificate signature
>
I notice that your virtual hosts are all using the ip address of your
machine, but your testing example uses http://localhost/
It's probably worth pointing out that localhost usually resolves to
127.0.0.1 which is not the same thing as your machine's ip address.
Try testing against https://192.1
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Sonu Kishore
> Sent: 11 September 2002 06:38
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [E
17 matches
Mail list logo
