Everyone,

I've run into the above error during my testing. (An unrecognized file or message encoding was found. User action: Correct the file or message)   I'll share the setup before I ask my question for discussion.

I get to pass a series of bytes in the hash that should be the TBS data of a certificate.

I get to pass the 256 byte signature that I need to validate.

I get to pass a certificate that should be able to validate the provided signature data.

Since TBS and the signature data are nothing but a series of bytes, I'm thinking that the 881 error does not apply.  This then leads me to believe this error applies to the certificate that was provided for the API call.

This document appears to be a X.509 wrapped in a PKCS#7 envelope.     I have passed what I believe are straight X.509 certificates to this interface before and I have a different error I'm tracking down for those tests.  And are not part of this discussion at this time.

I'm left wondering:   Does the DSV interface accept PKCS#7 wrapped X.509 certificates as easily as it does the native X.509 certificate, or do I need to extract the X.509 certificate from the PKCS#7 envelope so I can get the DSV call to accept the certificate?

If anyone knows the answer to this, I would appreciate the help.

Sincerely,

Mark Vollmer

The PKA_public_key_identifier must be a native X.509 certificate, either DER-encoded (binary) or PEM-encoded (printable EBCDIC).

Everyone,

I've run into the above error during my testing. (An unrecognized file or message encoding was found. User action: Correct the file or message)   I'll share the setup before I ask my question for discussion.

I get to pass a series of bytes in the hash that should be the TBS data of a certificate.

I get to pass the 256 byte signature that I need to validate.

I get to pass a certificate that should be able to validate the provided signature data.

Since TBS and the signature data are nothing but a series of bytes, I'm thinking that the 881 error does not apply.  This then leads me to believe this error applies to the certificate that was provided for the API call.

This document appears to be a X.509 wrapped in a PKCS#7 envelope.     I have passed what I believe are straight X.509 certificates to this interface before and I have a different error I'm tracking down for those tests.  And are not part of this discussion at this time.

I'm left wondering:   Does the DSV interface accept PKCS#7 wrapped X.509 certificates as easily as it does the native X.509 certificate, or do I need to extract the X.509 certificate from the PKCS#7 envelope so I can get the DSV call to accept the certificate?

If anyone knows the answer to this, I would appreciate the help.

Sincerely,

Mark Vollmer