Re: cms signing error with SHA3-512 & PSS

On 1/21/26 5:40 PM, 'Harald Koch' via openssl-users wrote:
> Hello Matt,
> ...
>> The reason can be seen in the code here:
>>
>> https://github.com/openssl/openssl/blob/b2ecef451ccede07366023da4553f113f6e4fe71/providers/common/der/der_rsa_key.c#L321-L345
>>
>> We hit the default case above and error out. Following the link in 
>> the comment brings you to RFC8017:
>>
>> https://tools.ietf.org/html/rfc8017#appendix-A.2.1
>>
>> "hashAlgorithm identifies the hash function.  It SHALL be an 
>> algorithm ID with an OID in the set OAEP-PSSDigestAlgorithms."
>>
>> Below that sentence is the set of algorithms, which does not include 
>> any SHA3 algorithms.
> The list in the RFC also has a line "...  -- Allows for future 
> expansion —„, which implies more digest algorithms to be added. 
> SHA33-512 can be identified as 2.16.840.1.101.3.4.2.10 
> (https://oid-base.com/get/2.16.840.1.101.3.4.2.10).

This is a matter of interpretation, isn't it?  Does "future expansion" 
mean ad-hoc, or by newer RFCs?

Ad-hoc could of course be done, if it's safe to assume the same 
PARAMETERS NULL as for all others (I agree that this is a safe bet, but 
one never really knows, yeah?).  But either way, OpenSSL providers 
currently lean on the safe side of algos specified by RFCs, rather than 
ad-hoc expansion.  (I think this is library policy)

Cheers,
Richard

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/9689d563-e2d2-412c-b5d9-699f97ce84c3%40levitte.org.