Re: cms signing error with SHA3-512 & PSS

Hello Richard,

> Am 22.01.2026 um 08:41 schrieb Richard Levitte <[email protected]>:
> 
> 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)
> 
Since at least Bouncycastle supports this algorithm, I assume their library policy allows the usage of additional OIDs (so do I). If it is a simple task to add it to the list of support algorithms, may it be possible for me to do so (if openSSL doesn’t want to go the same way)? This way I would have a functional framework and could wait for an official implementation. I have to keep up compatibility and want to stay with openSSL.

Greetings,
Harald


-- 
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/513A59F7-71CA-46FB-B379-90D2DD01316A%40c-works.net.