IETF Logo Mail Archive

[COSE] Re: c509 example verification

Derek Atkins <derek@ihtfp.com> Mon, 29 July 2024 20:35 UTC

Return-Path: <derek@ihtfp.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 E0C7CC15152C for <cose@ietfa.amsl.com>; Mon, 29 Jul 2024 13:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOH1m5BYNoJJ for <cose@ietfa.amsl.com>; Mon, 29 Jul 2024 13:35:38 -0700 (PDT)
Received: from mail.ihtfp.org (MAIL.IHTFP.ORG [204.107.200.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8700EC151092 for <cose@ietf.org>; Mon, 29 Jul 2024 13:35:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.ihtfp.org (Postfix) with ESMTP id BFD29806C243; Mon, 29 Jul 2024 16:35:36 -0400 (EDT)
Received: from mail.ihtfp.org ([127.0.0.1]) by localhost (mail.ihtfp.org [127.0.0.1]) (maiad, port 10024) with LMTP id 1377135-06; Mon, 29 Jul 2024 16:35:36 -0400 (EDT)
Received: by mail.ihtfp.org (Postfix, from userid 48) id 9A36C806C25D; Mon, 29 Jul 2024 16:35:36 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.ihtfp.org 9A36C806C25D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1722285336; bh=lVDAEDp/SG0UD0FA8qPs0pvJRgTFow11JV2PJz1SkCA=; h=In-Reply-To:References:Date:Subject:From:To:Cc:From; b=RrZvZ20/hkEHD/Gleg17Dgmrs3yvTr705/YaUQykFndai8wFlsEak3kcmnBRRTX93 IXu6w1/3nY/U/kmQiviLBWzzyv+E3PdCxs0yDRstJN808Xo0dX7lwX8y8wUmdfVzto 8nsf5L+H74gtorNzKZ2hZ4VcVA18ZXoLuJOqMA0c=
Received: from 192.168.248.188 (SquirrelMail authenticated user warlord) by mail.ihtfp.org with HTTP; Mon, 29 Jul 2024 16:35:36 -0400
Message-ID: <6ff5d0d6147043b51b52c2089d17ac06.squirrel@mail.ihtfp.org>
In-Reply-To: <CANNx7D-XLKsx2NwToSmJG_yy1T9Q-_F-vG1Cy4mj-1t2fvsZKA@mail.gmail.com>
References: <af3f955063764210bc35e5a3368fda1a@jhuapl.edu> <CANNx7D-XLKsx2NwToSmJG_yy1T9Q-_F-vG1Cy4mj-1t2fvsZKA@mail.gmail.com>
Date: Mon, 29 Jul 2024 16:35:36 -0400
From: Derek Atkins <derek@ihtfp.com>
To: Lijun Liao <lijun.liao@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]-6.fc34.20190710
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Message-ID-Hash: FYMTGKR3SJQ4OIYLSAV62ILMXRGJUM32
X-Message-ID-Hash: FYMTGKR3SJQ4OIYLSAV62ILMXRGJUM32
X-MailFrom: derek@ihtfp.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cose.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Sipos, Brian J." <brian.sipos@jhuapl.edu>, cose@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [COSE] Re: c509 example verification
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/dF30vuqIcKFJw2HIT6Q7T7aj_sI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Owner: <mailto:cose-owner@ietf.org>
List-Post: <mailto:cose@ietf.org>
List-Subscribe: <mailto:cose-join@ietf.org>
List-Unsubscribe: <mailto:cose-leave@ietf.org>

Ditto-- I have some private tools for reading C509 certs that I could use,
at least to see if my implementation will accept them or not.  We do use
SAN, although not "OTHER_NAME".

-derek

On Mon, July 29, 2024 4:28 pm, Lijun Liao wrote:
> Please attach your c509 certificate, if allowed. I have some private tools
> to do the analysis.
>
> Sipos, Brian J. <Brian.Sipos@jhuapl.edu> schrieb am Mo., 29. Juli 2024,
> 22:19:
>
>> All,
>>
>> I’m looking into creating some example c509 certificates which make use
>> of
>> SAN Other Name and EKU code points allocated by the current draft [1]
>> for
>> BP security. I think I have a properly encoded c509 structure using
>> native
>> signature, but don’t have a good way to verify that correctness.
>>
>> I tried using the tool under “c509_demo_impl” of the c509 source repo
>> [2]
>> but just get errors when attempting to use it in the read-C509 mode with
>> “cargo r c …” and I’m not sure what I may be doing wrong (it’s not clear
>> if
>> the input is supposed to be direct binary, which I have tried, or some
>> other form of text-encoding). Any help getting this tool, or some other
>> more appropriate tool, working would be appreciated.
>>
>> Brian S.
>>
>>
>>
>> [1]
>> https://www.ietf.org/archive/id/draft-ietf-cose-cbor-encoded-cert-11.html
>>
>> [2] https://github.com/cose-wg/CBOR-certificates
>>
>>
>> _______________________________________________
>> COSE mailing list -- cose@ietf.org
>> To unsubscribe send an email to cose-leave@ietf.org
>>
> _______________________________________________
> COSE mailing list -- cose@ietf.org
> To unsubscribe send an email to cose-leave@ietf.org
>


-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant

v2.46.0 | Report a Bug | By Email | System Status