EldoS | Feel safer!

Software components for data protection, secure storage and transfer

No signer certificates' identifiers found on PDF

Also by EldoS: BizCrypto
Components for BizTalk® and SQL Server® Integration Services that let you securely store and transfer information in your business automation solutions.
#17135
Posted: 07/26/2011 10:32:55
by Milan Kovarik (Basic support level)
Joined: 07/13/2011
Posts: 9

Hi,

I have a PDF with one signature. In that PDF I don't get a ElPKCS7Issuer from ElPDFPublicKeySecurityHandler via ElPDFPublicKeySecurityHandler.CertIDs property.

I simulate my problem on PDFBlackBox TineProcessor sample.

Code
TElPDFSignature sig = (TElPDFSignature)(objects[cbSignatures.SelectedIndex]);
         if (sig.Validate())
         {
            if (sig.Handler is TElPDFPublicKeySecurityHandler)
            {

               SecHandler = (TElPDFPublicKeySecurityHandler)sig.Handler;

               for (j = 0; j < SecHandler.CertIDCount; j++)
               {
}}}


Signature is validated with result true, sig.Handler is set but doesn't contain any CertIDs (expected one).

What's wrong please? Are there missing any meta information about Issuer, SN in my PDF?

I can send you given PDF, but it's confidential, so I can't attach it to conference..

Thank you,

Milan Kovarik
#17136
Posted: 07/26/2011 11:05:59
by Eugene Mayevski (EldoS Corp.)

Let's continue in HelpDesk where you can post the PDF confidentially. I'll create a ticket for you there.


Sincerely yours
Eugene Mayevski
#17137
Posted: 07/26/2011 11:24:36
by Raymond Lee (Basic support level)
Joined: 07/26/2011
Posts: 1

Hi Eugene,

Would you post the update or result for this problem?

Because we are considering to use SecureBlackBox, we need to know
the cause of this kind of problem in "signer identifier".

Thanks,
Raymond
#17138
Posted: 07/26/2011 12:11:48
by Eugene Mayevski (EldoS Corp.)

Different reasons can exist, and it's possible that this particular resolution is not applied at all to other similar cases.


Sincerely yours
Eugene Mayevski
#17151
Posted: 07/27/2011 04:46:39
by Eugene Mayevski (EldoS Corp.)

In this particular case the document was signed using PKCS#1 (plain RSA key), not PKCS#7 (certificate). Consequently, PKCS#7 attributes were not available.

But as said this case (and this cause) is not applicable to all cases with similar symptoms.


Sincerely yours
Eugene Mayevski
Also by EldoS: Callback File System
Create virtual file systems and disks, expose and manage remote data as if they were files on the local disk.

Reply

Statistics

Topic viewed 810 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!