Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates
 209.85.210.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHP4M8Um8JSTVCutzjx2WctyUv6_rDb=XM-+okyYARvuZsAjMQ@mail.gmail.com>
References: 
 <CAHP4M8Um8JSTVCutzjx2WctyUv6_rDb=XM-+okyYARvuZsAjMQ@mail.gmail.com>
Date: Sun, 25 Mar 2012 14:09:07 -0400
Message-ID: 
 <CALK=YjOgf_KQGXTKih5OZp0r=O9e=5CJEATvdoyiNpKJXjcuhg@mail.gmail.com>
From: Eric Covener <covener@gmail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [users@httpd] How does client decrypt data in a HTTPS-based
 WebDAV transfer

> BUT, HOW IS THE CLIENT ABLE TO DECRYPT THE DATA? (I have been running both
> webdav server and client on the same machine; so it might very well
> be the case that some info from "ssl.conf" and/or "httpd.conf" is being used
> at the client side. However, I am just guessing ...

Under SSL, the client and server negotiate a shared secret used to
encrypt/decrypt the data.

They can set this up securely because the client starts this process
with info encrypted with the servers public key.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org