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 1ECC717769 for ; Wed, 8 Oct 2014 13:57:34 +0000 (UTC) Received: (qmail 37111 invoked by uid 500); 8 Oct 2014 13:57:25 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 37077 invoked by uid 500); 8 Oct 2014 13:57:25 -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 37067 invoked by uid 99); 8 Oct 2014 13:57:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2014 13:57:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of de.techno@gmail.com designates 209.85.220.48 as permitted sender) Received: from [209.85.220.48] (HELO mail-pa0-f48.google.com) (209.85.220.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2014 13:57:19 +0000 Received: by mail-pa0-f48.google.com with SMTP id eu11so9090746pac.35 for ; Wed, 08 Oct 2014 06:56:58 -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:references :in-reply-to:content-type; bh=/pmP9bFKohIvSCLpGyGte28Y9tzc/gVjD7mVHdgh9gc=; b=oVO2X/9r0AyM1r7l+XiLpLY650v9rdle0haVLrZfrF1wPqnpa2z0ByFqmh+RW8Fl7f 3zl1mXp8yryv0DEazIZeUTPLduIpxOTTlh84yHXo9MYPf6PnbRcVHNrqjhCXqx5YsJqX 9R8qpZuaMMfBc2JapBvii6lu6XMejklWcsBUOzHEZlj6WD8yVe8FDvZaNqlHInlxuHn6 E177yqG3sSHUFKovgzR14XpxY8hTCo34+s2JhRuCoZlt87r1AcSiRX9MXfBRqwdKGCRC ny/RnL3QacPPVmxlX6jbpObIN6wRsFlswgCKyGn9bOBwlHgljlvDz6DPWAdW8GgGjt7W rAHA== X-Received: by 10.66.228.103 with SMTP id sh7mr10660881pac.98.1412776617150; Wed, 08 Oct 2014 06:56:57 -0700 (PDT) Received: from [192.168.1.2] ([117.208.68.252]) by mx.google.com with ESMTPSA id kk10sm101682pdb.63.2014.10.08.06.56.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Oct 2014 06:56:56 -0700 (PDT) Message-ID: <54354295.2010709@gmail.com> Date: Wed, 08 Oct 2014 19:26:37 +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 References: <54351612.80704@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060407080200020701020205" X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Intended use of SSLCACertificateFile/SSLCACertificatePath --------------060407080200020701020205 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/08/14 16:53, Eric Covener wrote: > > On Wed, Oct 8, 2014 at 6:46 AM, dE > wrote: > > Are all SSLCA* directives used for the same purpose (where client > sends the public key for it's authentication)? > > > ​No.​ > Thanks for clarifying that. --------------060407080200020701020205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 10/08/14 16:53, Eric Covener wrote:

On Wed, Oct 8, 2014 at 6:46 AM, dE <de.techno@gmail.com> wrote:
Are all SSLCA* directives used for the same purpose (where client sends the public key for it's authentication)?

​No.​


Thanks for clarifying that.
--------------060407080200020701020205--