IETF Logo Mail Archive

Re: [Trans] v2 SCTs and v1 SCTs distinguishability

"Salz, Rich" <rsalz@akamai.com> Thu, 12 August 2021 20:22 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6753A48A1 for <trans@ietfa.amsl.com>; Thu, 12 Aug 2021 13:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 3QKubCocNwT7 for <trans@ietfa.amsl.com>; Thu, 12 Aug 2021 13:22:06 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C29843A489E for <trans@ietf.org>; Thu, 12 Aug 2021 13:22:06 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 17CKG2E8002617; Thu, 12 Aug 2021 21:21:55 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=xfKxlhHtibFkgTx1R4kFJfFBl7mlcVkPvz1ppE6v5S0=; b=KqZZ0zkSFq32XX7kmSnpXouAkBvK3Bgmz7c8BGsFf9QpvGZsTi6+BaE/3oATXpPbBUdB SiVWfXy/bCKMyEu76X+LfTNY0HJ+5Or9ZoGXB6Q3RVlrM28DupUItfh06H/NZSj3r9CD bqKtFyDYKXJUIPwmxgqMFo/0Qye9TDvl/4SAEgodeOjIs9gu/GWpx/f1mmuKIkIkabeJ CjJ1nnT2rpXaW0+lGizkacmNydkAzOjUuz+8w3E4M2DY2xc+iodrm42bVAp+2nmCt9MW /Nx3rrDZpDdFLPpBoPAl3p7j85y2eLc/r7kk13TlRlmraFvJ71y8cV+t+gXliJW740Xw 5A==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 3acxeb50xw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 12 Aug 2021 21:21:54 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 17CKJGPD016391; Thu, 12 Aug 2021 16:21:53 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.113]) by prod-mail-ppoint3.akamai.com with ESMTP id 3acdhg2d25-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 12 Aug 2021 16:21:53 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.165.120) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Thu, 12 Aug 2021 15:21:52 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.023; Thu, 12 Aug 2021 15:21:52 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "trains@airmail.cc" <trains@airmail.cc>, "trans@ietf.org" <trans@ietf.org>
Thread-Topic: [Trans] v2 SCTs and v1 SCTs distinguishability
Thread-Index: AQHXj7ONlY14QjycwEOUKp55cUHKbKtwYLqA
Date: Thu, 12 Aug 2021 20:21:52 +0000
Message-ID: <157A1E67-8C74-4209-B64E-17F39EEF1524@akamai.com>
References: <1bb0f57710cdf3967fc23a7b8c7e859d@airmail.cc>
In-Reply-To: <1bb0f57710cdf3967fc23a7b8c7e859d@airmail.cc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.52.21080801
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4F9EC0103DB16D4CB0A54BC6A92E0E08@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-12_06:2021-08-12, 2021-08-12 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 adultscore=0 bulkscore=0 malwarescore=0 spamscore=0 mlxlogscore=730 suspectscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108120132
X-Proofpoint-ORIG-GUID: yUFVaYAU_CiRRgMLG-G0fS7GdCZE3IGb
X-Proofpoint-GUID: yUFVaYAU_CiRRgMLG-G0fS7GdCZE3IGb
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-08-12_06:2021-08-12, 2021-08-12 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 spamscore=0 priorityscore=1501 bulkscore=0 clxscore=1011 mlxscore=0 malwarescore=0 phishscore=0 impostorscore=0 suspectscore=0 mlxlogscore=674 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108120132
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.31) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint3
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/D8VYzwnaybRHmXZXDNliXJ7HmNg>
Subject: Re: [Trans] v2 SCTs and v1 SCTs distinguishability
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 12 Aug 2021 20:22:12 -0000

I think you are confusing the bytes on-the-network compared.

>So v1 SCTs and v2 structures both still have zero as the first byte,
unless you change v2 to reserve the range 0x0000 to 0x00FF, not just
0x0000.

In the network representation, yes, but not when it's in internal/native format.

v2.23.0 | Report a Bug | By Email