IETF Logo Mail Archive

Re: [TLS] TLS 1.2 hash agility

Mike <mike-list@pobox.com> Thu, 27 September 2007 17:21 UTC

Return-path: <tls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iax3d-0000Bm-OX; Thu, 27 Sep 2007 13:21:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iax3c-0008RC-0E for tls@ietf.org; Thu, 27 Sep 2007 13:21:48 -0400
Received: from sceptre.pobox.com ([207.106.133.20]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iax3H-0008Tc-KV for tls@ietf.org; Thu, 27 Sep 2007 13:21:27 -0400
Received: from sceptre (localhost.localdomain [127.0.0.1]) by sceptre.pobox.com (Postfix) with ESMTP id 04D8F2EF; Thu, 27 Sep 2007 13:21:49 -0400 (EDT)
Received: from [192.168.1.8] (wsip-24-234-114-35.lv.lv.cox.net [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sceptre.sasl.smtp.pobox.com (Postfix) with ESMTP id A74727FE7B; Thu, 27 Sep 2007 13:21:47 -0400 (EDT)
Message-ID: <46FBE66F.1040501@pobox.com>
Date: Thu, 27 Sep 2007 10:20:47 -0700
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Eric Rescorla <ekr@networkresonance.com>
Subject: Re: [TLS] TLS 1.2 hash agility
References: <46ABB82D.8090709@pobox.com> <46ACCCCB.8000201@pobox.com> <B356D8F434D20B40A8CEDAEC305A1F24046B2496@esebe105.NOE.Nokia.com> <20070914215611.0342933C21@delta.rtfm.com> <46EB102E.2070900@pobox.com> <20070914225606.9E9B433C21@delta.rtfm.com> <46EC2AE7.9040903@pobox.com> <20070917185820.6E7CC33C3A@delta.rtfm.com> <46FA745A.3070305@pobox.com> <20070926152907.8A60B33C23@delta.rtfm.com> <46FA91E8.5020303@pobox.com> <46FB4397.6040203@pobox.com> <46FBBBBE.7000108@pobox.com> <20070927143028.7EF4433C21@delta.rtfm.com> <46FBC5A1.7020501@pobox.com> <20070927161005.7CB8C33C28@delta.rtfm.com> <46FBDF1F.4050604@pobox.com>
In-Reply-To: <46FBDF1F.4050604@pobox.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

>> Remember that the signature over
>> the client's certificate and CertificateVerify is for the client's 
>> benefit, not the servers, and vice versa....
> 
> I thought that the signature over the client's certificate
> was to prove to the server that you have the corresponding
> private key, and therefore that you are the entity named in
> the certificate (and deserve access to private information
> about that entity).

Oops, I meant signature in CertificateVerify.

Mike

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

v2.35.0 | Report a Bug | By Email | System Status