Alberto Leiva wrote:
>
> 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 }).
I’ve been struggling with this, too. My conclusion was that RFC 7935 is
misleading at best. Section 5 of RFC 4055 talks about signature
algorithms not public key algorithms. Section 1.2 of RFC 4055 states
| The rsaEncryption object identifier continues to identify the subject
| public key when the RSA private key owner does not wish to limit the
| use of the public key exclusively to either RSASSA-PSS or RSAES-OAEP.
| In this case, the rsaEncryption object identifier MUST be used in the
| algorithm field within the subject public key information, and the
| parameters field MUST contain NULL.
So, for RSA v1.5, the key algorithm must be rsaEncryption. Routinator
does indeed require that. It doesn’t insist on the presence of the NULL,
though, and allows absent parameters.
The certificates we are generating in Krill will all have rsaEncryption
as the algorithm and the NULL paramteres field.
Kind regards,
Martin
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
