Re: [pkix] OID encoding help

Robert Moskowitz <rgm-sec@htt-consult.com> Mon, 08 May 2023 00:33 UTC

Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3909C14CF0C for <pkix@ietfa.amsl.com>; Sun, 7 May 2023 17:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 8Emo7MHW3fhb for <pkix@ietfa.amsl.com>; Sun, 7 May 2023 17:33:39 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 7CEE6C14CEED for <pkix@ietf.org>; Sun, 7 May 2023 17:33:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DEF726250B; Sun, 7 May 2023 20:33:14 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ABpqRzgYe5Ay; Sun, 7 May 2023 20:33:08 -0400 (EDT)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 5787E60944; Sun, 7 May 2023 20:33:06 -0400 (EDT)
Message-ID: <37998e7c-58b6-02de-69fa-1b2606123b39@htt-consult.com>
Date: Sun, 07 May 2023 20:33:25 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "pkix@ietf.org" <pkix@ietf.org>
References: <37ea5bd2-ac9e-4190-0936-5c04b1bffb9c@htt-consult.com> <SY4PR01MB62511401E87FE05AFCFDB91AEE709@SY4PR01MB6251.ausprd01.prod.outlook.com> <59c4f708-a8c2-07b7-029c-ee91b51a330d@htt-consult.com> <SY4PR01MB625149C145456DC9E64C196DEE709@SY4PR01MB6251.ausprd01.prod.outlook.com>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <SY4PR01MB625149C145456DC9E64C196DEE709@SY4PR01MB6251.ausprd01.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/lWHV80xRZk7oxngPSMpgHkPeWKA>
Subject: Re: [pkix] OID encoding help
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 May 2023 00:33:43 -0000


On 5/7/23 17:53, Peter Gutmann wrote:
> Robert Moskowitz <rgm-sec@htt-consult.com> writes:
>
>> Per my number above, shouldn't the last 3 bytes be 02 06 06  ?
> Ah, yeah, sorry, mistyped it.
>
>> Do I just concatinate these?  Or does the Endorsement need a length byte of
>> 7E in front of it?
> It depends on what the ASN.1 definition for it is, is it the usual type-and-
> value form?

With Russ' help, I believe it is all sorted now.

Then I had to work out how to get the base64 encoding needed for the 
CERT RR.  I believe that is all set.

I am really a hack at coding.  I do so little of it.   My serious joke 
is I never coded in 'C', only in 'B' (the Waterloo B compiler for 
Honeywell minis and mainframes back in the mid-80s).  And Python is 
really challenging in how it handles variable types. Particularly if you 
hack at it as seldom as I.

My scripts are at:

https://github.com/ietf-wg-drip/drip-scripts

and it is the endorse.py that makes the CERT RR.

Now to actually lay out the DNS structure for allowing full testing of DRIP.

I worked out some things late last week, and am now defining what I am 
calling the DRIP DKI (DRIP Key Infrastructure).

Follow my stumbling along on the DRIP wg list.

Bob