IETF Logo Mail Archive

Re: [lamps] WG Last Call for draft-ietf-lamps-pkcs12-pbmac1-02

Hubert Kario <hkario@redhat.com> Fri, 27 October 2023 13:23 UTC

Return-Path: <hkario@redhat.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3866EC14CE47 for <spasm@ietfa.amsl.com>; Fri, 27 Oct 2023 06:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 MMEGI92bvdPr for <spasm@ietfa.amsl.com>; Fri, 27 Oct 2023 06:23:00 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3EC1C151533 for <spasm@ietf.org>; Fri, 27 Oct 2023 06:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1698412978; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=q8KBpaaRAUqOYcefu7CTonuE1yd1zUyGoNqtvL6hFQQ=; b=blCnmaIFy9A+r5hVl7NdwEBWFz3gTbURK8QTLmYJ6mggygDceSQLip/Vks4rEu2i6s6tBm nz14Jwi+9Lp96F7FXKHKB1aSoGBcu343Vihm6UvDXtzAqGELB8pn7d+v8rmzQqllnb2ZuF +L0LitCvDZcC1QIeHafhgpRvqEH2/7E=
Received: from mail-ej1-f72.google.com (mail-ej1-f72.google.com [209.85.218.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-661-g8us-iY3NC2Pawa2kux2BQ-1; Fri, 27 Oct 2023 09:22:57 -0400
X-MC-Unique: g8us-iY3NC2Pawa2kux2BQ-1
Received: by mail-ej1-f72.google.com with SMTP id a640c23a62f3a-9ae686dafedso153558566b.3 for <spasm@ietf.org>; Fri, 27 Oct 2023 06:22:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698412976; x=1699017776; h=content-transfer-encoding:user-agent:organization:references :in-reply-to:message-id:mime-version:date:subject:cc:to:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=SVw3T2oKCdxKGqVy2OTEmFyxvjXvyAadbw3PeCnvwAE=; b=Al4hLuHZdd2A7GOkMHMTYNFjiKBdCZB44LhO/5bO0qzjCn05hSqdWQckPRCvOWne7e uEQ8DxbgUJdkHeUb/uE6Xl+lAkOXdX94Hd2SNYDcF7KuEyFDi0SoaWhf2hWAod7deNck ZFTbKEpIu/4olYU54LQSIK8AZM6xUEDDlAk+nX4qpk6+7OsKSHpTVAlP0Kl/4g4TdZj+ I8gsWYvdUONusIU0qo0owwqVjrbfo+jV9p+cuqNFbgQ7Kd9HvbG6SPgr5fCbZkX4kB8f T9kXxvl9TbsEy+Al9dpck+TeBhkMW7qMyL4NUpyajLVe53k1tvP1E0shZXiwxPht/aPe 4BZg==
X-Gm-Message-State: AOJu0YwFigx0azkV5HKeOfoBaq+JW7yVM91MjOPEcewSUAJSAZk3p9Ay kFBMYeHMqqSc6BGqOJU3baW36qpk7O/RwwfXRz28dIEpGdePJrz1XUVofe5x2D3jaglnrRWyHIr xEMIC+o+NUNirpQ==
X-Received: by 2002:a17:906:4784:b0:9ba:65e:7529 with SMTP id cw4-20020a170906478400b009ba065e7529mr2376325ejc.68.1698412976418; Fri, 27 Oct 2023 06:22:56 -0700 (PDT)
X-Google-Smtp-Source: AGHT+IGhoSSarZ/54rTS4JpXZYX3brW84Y5DDmzIDdp9Sm8QPOTi2Ifl6Ml239rlciXj037CCvN2lg==
X-Received: by 2002:a17:906:4784:b0:9ba:65e:7529 with SMTP id cw4-20020a170906478400b009ba065e7529mr2376316ejc.68.1698412976137; Fri, 27 Oct 2023 06:22:56 -0700 (PDT)
Received: from localhost (nat-pool-brq-u.redhat.com. [213.175.37.12]) by smtp.gmail.com with ESMTPSA id f27-20020a170906085b00b009c387ff67bdsm1196374ejd.22.2023.10.27.06.22.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 27 Oct 2023 06:22:55 -0700 (PDT)
From: Hubert Kario <hkario@redhat.com>
To: Russ Housley <housley@vigilsec.com>
Cc: Sean Turner <sean@sn3rd.com>, LAMPS <spasm@ietf.org>
Date: Fri, 27 Oct 2023 15:22:54 +0200
MIME-Version: 1.0
Message-ID: <5abf5cb7-7dce-47cd-99a6-cd68a9f8d733@redhat.com>
In-Reply-To: <45D7D39D-E675-4061-93E3-74F27557D01A@vigilsec.com>
References: <C61AE8CA-3692-43E0-ACE4-8BB0DEDB6D8B@vigilsec.com> <D33C746C-AEEB-4A19-A5ED-C7D949386F80@sn3rd.com> <45D7D39D-E675-4061-93E3-74F27557D01A@vigilsec.com>
Organization: Red Hat
User-Agent: Trojita/0.7-git; Qt/5.15.9; xcb; Linux; Fedora release 37 (Thirty Seven)
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/S3Lvfr3yXateEH2zQxa2kaTfnmY>
Subject: Re: [lamps] WG Last Call for draft-ietf-lamps-pkcs12-pbmac1-02
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2023 13:23:04 -0000

On Thursday, 26 October 2023 22:33:10 CEST, Russ Housley wrote:
> Sean:
>
> These can be imported from RFC 6268.

Should I do it? If yes, what's exactly expected?

(I do know that HMACs based on SHA-2 are already interoperable for PKCS#12,
both for MAC and for PBKDF2, so I don't understand what's missing...)

> Russ
>
>
>> On Oct 26, 2023, at 4:28 PM, Sean Turner <sean@sn3rd.com> wrote:
>> 
>> Hubert,
>> 
>> Hi! I was poking looking at the ASN.1 in RFC 5911 [0] and 8018 
>> [1] and I think maybe we need to define maca-hMAC-SHA256 / 
>> alg-hMAC-SHA256 for the prf field in PBKDF2-params.  Right now 
>> there’s only one value for pdf and it’s defined for 
>> maca-hMAC-SHA1 / alg-hMAC-SHA1. If it’s not in another RFC, 
>> then for RFC 5911 we’d need something like:
>> 
>> PBKDF2-PRFs ALGORITHM ::= { alg-hMAC-SHA1, alg-hMAC-SHA256, … }
>> 
>> maca-hMAC-SHA256 MAC-ALGORITHM ::= { ...
>
>
>

-- 
Regards,
Hubert Kario
Principal Quality Engineer, RHEL Crypto team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic

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