Skip to content

DefaultAlgorithmNameFinder and DefaultAlgorithmNameFinder do not have names for SM2 with SM3 #2377

Description

@mauromol

Very similar to #2306

While working with DefaultAlgorithmNameFinder and DefaultSignatureNameFinder, I found out that they have no mapping for SM2 with SM3 signature algorithm.
So, for example, if you do new DefaultAlgorithmNameFinder.getAlgorithmName(GMObjectIdentifiers.sm2sign_with_sm3) you just get "1.2.156.10197.1.501" instead of "SM3WITHSM2".
This is in contrast with what is handled by DefaultSignatureAlgorithmIdentifierFinder, which does support SM2 and SM3.

I'm using Bouncy Castle 1.85.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions