verify method in SignerInformation and provider implementing message digest

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

verify method in SignerInformation and provider implementing message digest

MACKO Roman
Hi,

I have noticed CMSSignedDataGenerator will look in the default provider
for a message digest implementation if the encryption provider doesn't
have one in release 1.28. It would be good if SignerInformation class
does the same in
verify method. It will help me to get rid of using next provider which
only takes implemetation of message digest
from one provider (e.g. BC provider) and the rest of methods from
encryption provider.

Thanks, Roman