IETF Logo Mail Archive

Re: [pkix] AuthorityKeyIdentifier and SubjectKeyIdentifier in DRIP X.509 certs

Robert Moskowitz <rgm-sec@htt-consult.com> Sun, 14 May 2023 23:46 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 49754C151096 for <pkix@ietfa.amsl.com>; Sun, 14 May 2023 16:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 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] 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 yg1XOD52LIaH for <pkix@ietfa.amsl.com>; Sun, 14 May 2023 16:46:19 -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 8CD18C151076 for <pkix@ietf.org>; Sun, 14 May 2023 16:46:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DBD5462574; Sun, 14 May 2023 19:45:54 -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 scLmKFaN6i6Q; Sun, 14 May 2023 19:45:50 -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 7411F6250B; Sun, 14 May 2023 19:45:50 -0400 (EDT)
Message-ID: <d959792c-d5b5-4548-5fc4-041bad401a8c@htt-consult.com>
Date: Sun, 14 May 2023 19:46:09 -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>, IETF PKIX <pkix@ietf.org>
References: <5728d335-f283-a8ce-b0b4-82a88e5f1525@htt-consult.com> <SY4PR01MB625132D16A3FDB3C64E7F2EDEE7B9@SY4PR01MB6251.ausprd01.prod.outlook.com>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <SY4PR01MB625132D16A3FDB3C64E7F2EDEE7B9@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/0T37wkEHbg-PGPzMY8LjHReXbC8>
Subject: Re: [pkix] AuthorityKeyIdentifier and SubjectKeyIdentifier in DRIP X.509 certs
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: Sun, 14 May 2023 23:46:21 -0000

Peter,

Your comments cleared up for me the obvious place I was getting aKID 
from.  From the signing cert!

ARGH!!

All I had to do was backtrack and create my signing cert with the fix I 
had done for sKID and now I have the chain I am looking for.

Some times I get lost in the weeds.

Thanks

On 5/14/23 19:30, Peter Gutmann wrote:
> Robert Moskowitz <rgm-sec@htt-consult.com> writes:
>
>> I SHOULD be able to use the DETS in keyIdentifier as I do with
>> SubjectKeyIdentifier, but openSSL is resisting my efforts.  So far.
> The aKID is copied from the issuing cert so I would imagine you can't just set
> it arbitrarily.  OTOH since the aKID is copied from the issuing cert the
> obvious way to get it into the subject cert would be to set it as the sKID in
> the issuing cert.
>
>> I was wondering if there is something I could do with authorityCertIssuer?
> Probably not for the same reason you can't set the aKID in the subject cert
> yourself.
>
> You then also run into the problem that the sKID/aKID is the universal
> identifier there and it's not clear what, if any, support there is for
> handling authorityCertIssuers.
>
> Peter.
>

v2.23.0 | Report a Bug | By Email