Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DFE7617FCB for ; Wed, 8 Oct 2014 10:47:38 +0000 (UTC) Received: (qmail 55515 invoked by uid 500); 8 Oct 2014 10:47:30 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 55478 invoked by uid 500); 8 Oct 2014 10:47:30 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 55468 invoked by uid 99); 8 Oct 2014 10:47:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2014 10:47:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of de.techno@gmail.com designates 209.85.192.172 as permitted sender) Received: from [209.85.192.172] (HELO mail-pd0-f172.google.com) (209.85.192.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2014 10:47:03 +0000 Received: by mail-pd0-f172.google.com with SMTP id ft15so6709828pdb.31 for ; Wed, 08 Oct 2014 03:47:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=QM8y0cXDUPFNnDr3hLtenQseR6mV0u5MD4snfBmESKk=; b=cu/+NMcosA2OH5Ee4oe7sVhkm9YSbB0d22LkTnRfRpKj7GMOvKkV9fiAIRtmdyqVzM rRZdv8T6A1KCT6RV+rjVNrDAajPXKD+C0S/yQ7PkVDytuBJtavX/AUByHdiy5i7ioeXa uD2ggxVfDneTSLE7NhBMRbDX9cz9ZiG81Xld7bu/d2o24dg/QVaWSJjW0f3JjfK47YRm dM72stN205wpDRPyaHB42/mCb59cX682cxCUTbLsomxwTvJm0ZS+my3h9AY4aqGRIDQ+ YjOdp9L/HhfrMHPTmOdlbIhMgAhtvIlPiO5DC2r4P7lOgFhWB6I3rILrscheUaoMR13k V4JQ== X-Received: by 10.70.131.101 with SMTP id ol5mr9860071pdb.77.1412765221002; Wed, 08 Oct 2014 03:47:01 -0700 (PDT) Received: from [192.168.1.2] ([117.208.68.252]) by mx.google.com with ESMTPSA id az8sm18641160pac.12.2014.10.08.03.46.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Oct 2014 03:47:00 -0700 (PDT) Message-ID: <54351612.80704@gmail.com> Date: Wed, 08 Oct 2014 16:16:42 +0530 From: dE User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.8.0 MIME-Version: 1.0 To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] Intended use of SSLCACertificateFile/SSLCACertificatePath In Apache 2.2, these can be used instead of SSLCertificateChainFile, but from it's documentation and mentioning of "clients", it looks like this's intended to be used in a situation where the client sends the server certificates for it's own authentication. This's what I get from -- "These are used for Client Authentication." Is this correct? Are all SSLCA* directives used for the same purpose (where client sends the public key for it's authentication)? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org