[sidr] rsaEncryption vs sha256WithRSAEncryption in RPKI certificates

Alberto Leiva <ydahhrk@gmail.com> Wed, 22 May 2019 22:18 UTC

Return-Path: <ydahhrk@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922F51200B8 for <sidr@ietfa.amsl.com>; Wed, 22 May 2019 15:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BgSpEHsqPZx4 for <sidr@ietfa.amsl.com>; Wed, 22 May 2019 15:18:46 -0700 (PDT)
Received: from mail-it1-x130.google.com (mail-it1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22F9612004A for <sidr@ietf.org>; Wed, 22 May 2019 15:18:46 -0700 (PDT)
Received: by mail-it1-x130.google.com with SMTP id i63so5542952ita.3 for <sidr@ietf.org>; Wed, 22 May 2019 15:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=XyFfy4r+cSZlUCdT75EP1lC1RfGsggvki4yRm+ERWTA=; b=DqzfwlEG9PUlPDDJBG9rb0leVVZlK9Vt4SSx/D3fewutaKR47xyF66881qKFU2HJhI B8vhs5hb84qdNUBvpblcA9+md8sqeT5z4bIycBj6hlPmbxKNVBnVcQlD7uMzih+6XwV0 G10OaxfDFSXZaiaSk6nMdk9vFwCOx25i8NrksQT6JkCXiuiHlHUIUSPHMc7Cl2NoauoX oogh6PQHbh/rmYz907nNTDr2po3mhxA/b6rphOMB0keFFwL2248B67avXkUDyFjLsQXt aP2i6bRidiV2x/hsxQ/IMeU42XN+Uj7bp4ZYA2nfnsiWg3vDXZa7LcHWJdS1TfYSOMdL 1d3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=XyFfy4r+cSZlUCdT75EP1lC1RfGsggvki4yRm+ERWTA=; b=Pp8Ot8FJ/hQyeSmg1iBQUZFbh6TQygIWcBukvin3CCjGNQ0/5Pb/AyDZ5aayxfObRv yqzTLGAHpiHgRiyAV8hlQQoB/gm/UVosCkaYvBko6uE9eyurfJhsVGGg/0PW2Aa4EzrA Ev2T8euuiopQ4cblz3d7kKpCvGBCOp9LePFHuWXvurHj53b8lp2gYCO83v6FabBN76M8 p5nw8rRLA9kRAy4GQcL3RaLwGPd5quc3Vv/vJNFRmss4YqLkDFrFwsDt6PPpDlsjURw9 zCJxCXv4OkA81W0JB9gM4LcEs5VcEwOz8YoLRyM0MElACDFw19Eq5IP0s93mIcIXWry3 SWHA==
X-Gm-Message-State: APjAAAXEDqtM2QMMnCQjAWdb9InMHOnJBg/txXW4WMSqFuYUY8pzX1Tq wbR41OZsWUdHjGAAnlQD7TVeYeasBl8OzVPYmJsh/xkc
X-Google-Smtp-Source: APXvYqxbIYXU3Yxp/wiV3TrQilykj9f9hjxNsIHeFPMrA02gnC0P3vJyWrHqawRUZaGmV4J7loNb5NK05LltUp6so48=
X-Received: by 2002:a02:1986:: with SMTP id b128mr61083089jab.136.1558563525216; Wed, 22 May 2019 15:18:45 -0700 (PDT)
MIME-Version: 1.0
From: Alberto Leiva <ydahhrk@gmail.com>
Date: Wed, 22 May 2019 17:18:34 -0500
Message-ID: <CAA0dE=VOCvxb_0-pEB8CO=JZ9FShVf=pQ43pCmAeYCf9LRTTcw@mail.gmail.com>
To: sidr@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/ENSRjlq9KgvRAyREVOIlrKLN7iw>
Subject: [sidr] rsaEncryption vs sha256WithRSAEncryption in RPKI certificates
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2019 22:18:48 -0000

Hello

Another question.

RFC 7935 states the following:

3.1.  Public Key Format

   (...)

   algorithm (which is an AlgorithmIdentifier type):
      The object identifier for RSA PKCS #1 v1.5 with SHA-256 MUST be
      used in the algorithm field, as specified in Section 5 of
      [RFC4055].  The value for the associated parameters from that
      clause MUST also be used for the parameters field.

I've never seen a certificate that declares sha256WithRSAEncryption ({
pkcs-1 11 }) as its public key algorithm. Every certificate I've come
across labels its algorithm as rsaEncryption ({ pkcs-1 1 }).

(Certificates always define the signature algorithm as
sha256WithRSAEncryption, but that's a different field.)

Is everyone doing it wrong, or am I missing something?

I'm aware that this is likely a triviality--rsaEncryption and
sha256WithRSAEncryption probably mean the same in this context.
There's also a thread in this list in which people seem to have
experienced headaches over this topic. But the thread is talking about
CMS signed objects (which I believe is different from certificates),
and happened before 7935 was released, so it feels like the RFC should
mandate something consistent with reality by now.

Thanks for any pointers.