IETF Logo Mail Archive

Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion

Paul Wouters <paul@nohats.ca> Sat, 14 March 2015 01:58 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE67F1A00F0 for <trans@ietfa.amsl.com>; Fri, 13 Mar 2015 18:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LNiVads02fR for <trans@ietfa.amsl.com>; Fri, 13 Mar 2015 18:58:04 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E9071A00DB for <trans@ietf.org>; Fri, 13 Mar 2015 18:58:03 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3l3n9441c6z28R; Sat, 14 Mar 2015 02:58:00 +0100 (CET)
Authentication-Results: mx.nohats.ca; dkim=pass reason="1024-bit key; unprotected key" header.d=nohats.ca header.i=@nohats.ca header.b=Jga1wn0T; dkim-adsp=pass
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id sP9uMnO_cIzZ; Sat, 14 Mar 2015 02:57:59 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sat, 14 Mar 2015 02:57:59 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id DE2AB80A01; Fri, 13 Mar 2015 21:57:58 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1426298278; bh=D7+xM7TEVYxD9GDfutfEgIM8Va4labL2YLL9ivqYHWQ=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Jga1wn0TbqfOxdBawyGUWtcWblWmutRq/srWaxV2BFj4946sABVenj/1RIUIpTlA2 IpAUH7ndO24RAD84L2ctWriktI2TAz00toNWbFr/gpvLdPDoPvpSE7b5+11cxgFl34 mMHhQnCQLp0x5D4HOAV82tDL0AfHV+bCdmHzIkVA=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id t2E1vwIj022805; Fri, 13 Mar 2015 21:57:58 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Fri, 13 Mar 2015 21:57:57 -0400
From: Paul Wouters <paul@nohats.ca>
To: Nico Williams <nico@cryptonector.com>
In-Reply-To: <20150314000210.GD3479@localhost>
Message-ID: <alpine.LFD.2.10.1503132156440.17274@bofh.nohats.ca>
References: <550257A0.8050401@gmail.com> <B87AFA6C-2B9F-474C-AE0F-BF07829CD139@vigilsec.com> <20150314000210.GD3479@localhost>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/-UnAYffcS9bEek0hNif3irux5kg>
Cc: trans@ietf.org
Subject: Re: [Trans] Bad Technical Decision: Closing out the SCT encoding discussion
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Mar 2015 01:58:05 -0000

On Fri, 13 Mar 2015, Nico Williams wrote:

> Indeed.  The fact that Certificate includes TBSCertificate without
> wrapping it in an OCTET STRING has caused problems before.

Can you share what problems this has caused before? That would be
a useful addition to this discussion.

Paul

v2.23.0 | Report a Bug | By Email