[OAUTH-WG] Server cret verification in 10.9
Eran Hammer <eran@hueniverse.com> Fri, 20 January 2012 23:47 UTC
Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC3621F8568 for <oauth@ietfa.amsl.com>; Fri, 20 Jan 2012 15:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KkS7mCGn9VQ for <oauth@ietfa.amsl.com>; Fri, 20 Jan 2012 15:47:00 -0800 (PST)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by ietfa.amsl.com (Postfix) with SMTP id 842A121F855A for <oauth@ietf.org>; Fri, 20 Jan 2012 15:47:00 -0800 (PST)
Received: (qmail 23547 invoked from network); 20 Jan 2012 23:47:00 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.47) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 20 Jan 2012 23:47:00 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT005.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Fri, 20 Jan 2012 16:46:49 -0700
From: Eran Hammer <eran@hueniverse.com>
To: OAuth WG <oauth@ietf.org>
Date: Fri, 20 Jan 2012 16:46:38 -0700
Thread-Topic: Server cret verification in 10.9
Thread-Index: AczXzbKA/SD1BhejQGqf1ifLs7XLXA==
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AAB9653D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E723453AAB9653DP3PW5EX1MB01E_"
MIME-Version: 1.0
Subject: [OAUTH-WG] Server cret verification in 10.9
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 23:47:01 -0000
Stephen asked: > (13) 10.9 says that the client MUST verify the server's cert which is fine. > However, does that need a reference to e.g. rfc 6125? > Also, do you want to be explicit here about the TLS server cert and thereby > possibly rule out using DANE with the non PKI options that that WG (may) > produce? Can someone help with this? I don't know enough to address. EHL
- [OAUTH-WG] Server cret verification in 10.9 Eran Hammer
- Re: [OAUTH-WG] Server cret verification in 10.9 Peter Saint-Andre
- Re: [OAUTH-WG] Server cret verification in 10.9 John Bradley
- Re: [OAUTH-WG] Server cret verification in 10.9 Eran Hammer
- Re: [OAUTH-WG] Server cret verification in 10.9 John Bradley