[COSE] COSE X509 x5t hash algorithm identifier
Brian Sipos <brian.sipos+ietf@gmail.com> Wed, 09 February 2022 03:01 UTC
Return-Path: <brian.sipos@gmail.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 73F0B3A083B
for <cose@ietfa.amsl.com>; Tue, 8 Feb 2022 19:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, 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=gmail.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 liShNwocoOTM for <cose@ietfa.amsl.com>;
Tue, 8 Feb 2022 19:01:55 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com
[IPv6:2607:f8b0:4864:20::132])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 142873A0839
for <cose@ietf.org>; Tue, 8 Feb 2022 19:01:55 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id z7so623133ilb.6
for <cose@ietf.org>; Tue, 08 Feb 2022 19:01:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:from:date:message-id:subject:to;
bh=DCL+Dw3p5JXZz6RMHUMTe1eqU+/vTcNeXHCwiNy+86I=;
b=q4Mu7evYqIR96YZ4WnJ+ze1qcnFaSf1FOZgT1G1LJq1i2A513y0kDdbPXb44hzbil/
axgJhdPAKTJHB7JjkwtLD+dg+AScHWxHFu0byHPCViDhrpsk7gpp2ulZCR6oRN0bvpdR
8TWHgdJu2s4qVNCi68gacSToT++knV9n9XjVCkTxvwBjiQGW6Cw5ChwTDwNltVOveep/
WZ/9se89+85ro34RA/+DDgZb58juzlnnkDiRe6ad/EWsTUdN6PV4GL1VQF9U2ZWLLwiO
oQ5xq2G/zdRS6rXUKhZo+k20oKCLCDuRRF2sPTUVylc1yaYT1xKN+hFTpeWmob4zmgnd
fdLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=DCL+Dw3p5JXZz6RMHUMTe1eqU+/vTcNeXHCwiNy+86I=;
b=iDQ6NfWXrZrMb7W7k0MeaDbxUmPFl9IXEc9PQRuv74vD83lKqcnDeKUSeKbD82sN/Q
zSHU0+dTl4dIaYRZIiZGXIUFrU5ZZlJdFh8nPgga5UM6u5Vb4fTRRP8P0P/cQrBfifq0
4SQciSAPcG/hty1svqINy+410kQRMrwjJonHRk0EclXbXVBbWUHIqCzEpCy//uoFUcZV
aZUJl7eHGxe8X28Vq5OHQvAXJlbVPj0EKao+k7kAos+KD7oKkUGjzcoYpvKnJACoprAW
qMopPHrxxmtdutZUDilEyc3/7VYox9hEugOqDtoIRTGacurDZqXiK1cqSHck5klvjgWn
f2mw==
X-Gm-Message-State: AOAM531bP4TTkwHY7lybjAhGiELT58og3xryd+fMrNGvtK4SJ2vUW7ui
fBKs/mKQYqS7XKinLBq88PoI0my1OLXRi+h10Nqt02CdDv8=
X-Google-Smtp-Source: ABdhPJzP0jhzFGeQpeMmwkUokGf4dTSr305sfBuMgoCVacUaQXO+Ur02NGXQkGN0keIVKgtF5udSq/ZlKr/p+mHJNQg=
X-Received: by 2002:a92:c263:: with SMTP id h3mr99556ild.197.1644375712729;
Tue, 08 Feb 2022 19:01:52 -0800 (PST)
MIME-Version: 1.0
From: Brian Sipos <brian.sipos+ietf@gmail.com>
Date: Tue, 8 Feb 2022 22:01:41 -0500
Message-ID: <CAM1+-gis+QZMxAQr6nuh87jQxTypUHjQmE5xYYgwcpCVtQt+6Q@mail.gmail.com>
To: cose@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003c0d5405d78d0e6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/fkUB3VI3NZdp-DB1G7lMpuxvKi4>
Subject: [COSE] COSE X509 x5t hash algorithm identifier
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>,
<mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>,
<mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2022 03:02:00 -0000
All, While attempting to use the same kind of hash algorithm agility as the COSE X509 draft "x5t" parameter [1], I ran into a technical issue that I wrote up in a ticket [2]. I realize that I just missed the COSE interim to be able to discuss this, but I think this is a simple issue with (hopefully) a simple valid/invalid disposition. If valid and it would be helpful for me to submit a PR, please let me know. Thanks, Brian S. [1] https://www.ietf.org/archive/id/draft-ietf-cose-x509-08.html#section-2-5.5 [2] https://github.com/cose-wg/X509/issues/46
- [COSE] COSE X509 x5t hash algorithm identifier Brian Sipos
- Re: [COSE] COSE X509 x5t hash algorithm identifier Laurence Lundblade