Re: [COSE] Looking for COSE libraries and open source implementations

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 27 July 2021 16:06 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 EE9583A1064 for <cose@ietfa.amsl.com>; Tue, 27 Jul 2021 09:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 sSeEHVmVF1bf for <cose@ietfa.amsl.com>; Tue, 27 Jul 2021 09:06:38 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B5953A1058 for <cose@ietf.org>; Tue, 27 Jul 2021 09:06:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id EA60D389B7; Tue, 27 Jul 2021 12:10:21 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4oGB-EJ6Cknf; Tue, 27 Jul 2021 12:10:18 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7080A389B4; Tue, 27 Jul 2021 12:10:18 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 722AF440; Tue, 27 Jul 2021 12:06:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: g_e_montenegro=40yahoo.com@dmarc.ietf.org, cose <cose@ietf.org>
In-Reply-To: <962D86DE-8A1C-4782-BE27-135EC3AA9ED4@island-resort.com>
References: <005501d78220$09496bd0$1bdc4370$.ref@yahoo.com> <005501d78220$09496bd0$1bdc4370$@yahoo.com> <962D86DE-8A1C-4782-BE27-135EC3AA9ED4@island-resort.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 27 Jul 2021 12:06:32 -0400
Message-ID: <13619.1627401992@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/rBtbtiDOTCoc2DOJ2klESzc7r28>
Subject: Re: [COSE] Looking for COSE libraries and open source implementations
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: Tue, 27 Jul 2021 16:06:43 -0000

    > I’m looking at COSE versus more traditional alternatives, pros and
    > cons, and a huge cons would be access to open source implementations
    > and libraries.
    >
    > Anybody know of a good source of information about COSE libraries and
    > open source implementations?

I implement enough COSE (Sign1 only) to do RFC8366/Constrained-Vouchers at:
   https://github.com/AnimaGUS-minerva/ChariWTs

I also use https://github.com/AnimaGUS-minerva/cbor-rust
from https://github.com/franziskuskiefer/cbor-rust (Mozilla).

I think that you'll find that COSE is rather a swiss-army-knife kit, and that
many users will implement (and test) what they need, and leave the rest
aside.
Given the constrained focus of COSE, you may never see an all-singing library.

Also, the way in which COSE integrates with CBOR libraries probably depends
heavily on exactly how the data will be used.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide