Replies: 1 comment
-
|
We'd just need the AlgorithmIdentifier that describes this one... I don't actually know if there is one though. You could allocate a proprietary one. You do need one though, CMS requires an ASN.1 definition for the algorithm in order to create the encoded message. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm trying to do a signing process by using SignerInfoGenerator to create an S/MIME-message with said signing algorithm. When trying to instantiate a ContentSigner by using the JcaContentSignerBuilder I get an exception:
The algorithm itself seems to be supported in general, because
Signature.getInstance("SHA1WITHRSA/ISO9796-2", "BC")happily returns an instance.DefaultSignatureAlgorithmIdentifierFinderdoesn't contain a maping forSHA1WITHRSA/ISO9796-2. Is this intentional or can this be added? Can I in some way pass theSignatureinstance to theJcaContentSignerBuilderso that it doesn't need to do the lookup inDefaultSignatureAlgorithmIdentifierFinder?Beta Was this translation helpful? Give feedback.
All reactions