Re: [websec] #55: Clarify that the newest pinning information takes precedence
Yoav Nir <ynir@checkpoint.com> Fri, 29 March 2013 01:35 UTC
Return-Path: <ynir@checkpoint.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6087921F84F8 for <websec@ietfa.amsl.com>; Thu, 28 Mar 2013 18:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 r8qmBS6LQef3 for <websec@ietfa.amsl.com>; Thu, 28 Mar 2013 18:35:16 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC2B21F84F6 for <websec@ietf.org>; Thu, 28 Mar 2013 18:35:16 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r2T1ZDgr018594; Fri, 29 Mar 2013 04:35:13 +0300
X-CheckPoint: {5154EE21-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 29 Mar 2013 04:35:13 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: IETF WebSec WG <websec@ietf.org>
Thread-Topic: [websec] #55: Clarify that the newest pinning information takes precedence
Thread-Index: Ac2uQVh1gfgp5oAbRvq4qJa/hOeYpx86/5WAADfmVQA=
Date: Fri, 29 Mar 2013 01:35:13 +0000
Message-ID: <C05D5C8B-E5AF-4373-B448-058259B6D397@checkpoint.com>
References: <058.106749b7ec8d8775c9a7c03ff71b6de4@trac.tools.ietf.org> <073.ec94ba2e71513562888c29f0af0b3306@trac.tools.ietf.org>
In-Reply-To: <073.ec94ba2e71513562888c29f0af0b3306@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.21.137]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7A9F8FA7FADE2944956B2B834EA30729@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [websec] #55: Clarify that the newest pinning information takes precedence
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2013 01:35:17 -0000
The text works for me. On Mar 27, 2013, at 6:54 PM, websec issue tracker <trac+websec@grenache.tools.ietf.org> wrote: > #55: Clarify that the newest pinning information takes precedence > > > Comment (by palmer@google.com) > > Ryan Sleevi has added text to the working copy that I believe resolves > this ticket. Comments? > > https://code.google.com/p/key-pinning- > draft/source/diff?spec=svn4f697cf66f747c18a5389922f484d9a1dbe85968&r=83bad3527ede8bb6ef52a8c220990ccd8762d9e7&format=side&path > =/draft-ietf-websec-key-pinning.xml > > -- > -------------------------------+-------------------------------- > Reporter: palmer@google.com | Owner: palmer@google.com > Type: defect | Status: assigned > Priority: major | Milestone: > Component: key-pinning | Version: > Severity: - | Resolution: > Keywords: | > -------------------------------+-------------------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/55#comment:2> > websec <http://tools.ietf.org/websec/> > > _______________________________________________ > websec mailing list > websec@ietf.org > https://www.ietf.org/mailman/listinfo/websec
- [websec] #55: Clarify that the newest pinning inf… websec issue tracker
- Re: [websec] #55: Clarify that the newest pinning… websec issue tracker
- Re: [websec] #55: Clarify that the newest pinning… Chris Palmer
- Re: [websec] #55: Clarify that the newest pinning… websec issue tracker
- Re: [websec] #55: Clarify that the newest pinning… Tom Ritter
- Re: [websec] #55: Clarify that the newest pinning… Yoav Nir
- Re: [websec] #55: Clarify that the newest pinning… Chris Palmer
- Re: [websec] #55: Clarify that the newest pinning… Ryan Sleevi
- Re: [websec] #55: Clarify that the newest pinning… websec issue tracker