• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
3

Error during signature verification. Signature contains incorrect, unrecognized, corrupted or suspicious data. Support Information: SigDict /Contents illegal data

New Here ,
May 18, 2016 May 18, 2016

Copy link to clipboard

Copied

Hi Adobe,

We are using adbe.pkcs7.detached adding signature to the PDF. whenever I open signed PDF form it will show signature is unknown with below error code as

Error during signature verification. 

Signature contains incorrect, unrecognized, corrupted or suspicious data.

Support Information: SigDict /Contents illegal data

Can anyone confirm me issue w.r.t to the signature verification.

With regards

Ravi

TOPICS
Acrobat SDK and JavaScript , Windows

Views

37.3K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 01, 2020 Oct 01, 2020

Copy link to clipboard

Copied

Error during signature verification. Signature contains incorrect, unrecognized, corrupted or suspicious data. Support Information: SigDict /Contents illegal data

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 16, 2021 Apr 16, 2021

Copy link to clipboard

Copied

@Keshav_pki @Ravinder5FC4 @kadobe @vladan saveljic @Bernd Alheit @YatharthS 

Does anyone help me with this issue. If there is a solution already?

I have a signed PDF document along with Time-stamp and DSS. But when opened in Adobe reader, Signature is not valid and have the following error:

Signature contains incorrect, unrecognized, corrupted or suspicious data. Support Information: SigDict /Contents illegal data

 

I verified the Signature Field /Annot dictionary it seems normal. /Annot references a Signature dictionary via its /V field. And the Signature dictionary has /Type /Sig which constains all the mandatory fields.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Apr 16, 2021 Apr 16, 2021

Copy link to clipboard

Copied

Please share a representative example PDF for your issue.
There are multiple reasons for that message; as it says itself, it's probably merely something unknown to Adobe (e.g. EC signatures with brainpool curves) while other validation services may know these details and can validate without an issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 16, 2021 Apr 16, 2021

Copy link to clipboard

Copied

@MikelKlink Thanks for asking details and trying to help. Unfortunaetly, I couldn't re-create a PDF document with the same issue and I am not allowed to share the original document as it is a confidential data.

 

Despite this, would you like to suggest some investigative methods that I can try to find the root cause? 

Many thanks.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Apr 16, 2021 Apr 16, 2021

Copy link to clipboard

Copied

As mentioned above, very many reasons are possible, so if you cannot share the document in question here, you should contact someone knowledgeable in respect to integrated PDF signatures and present the document to them (under a NDA) for analysis.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 16, 2021 Apr 16, 2021

Copy link to clipboard

Copied

Ok thanks for your suggestions. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 25, 2022 Nov 25, 2022

Copy link to clipboard

Copied

Can you pls suggest other validation services pls!! it would be of great help.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

quote

Can you pls suggest other validation services pls!! it would be of great help.

Suggesting other validation services makes only sense after inspecting the signed PDF in which Adobe Acrobat sees "illegal data".

Thus, please share an representative example of your problem PDFs for analysis. Depending on the analysis result, a suggestion may be possible.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 07, 2021 Jul 07, 2021

Copy link to clipboard

Copied

Hello everyone, i'm having the same issue with digital signatures in Acrobat Reader..."Signature contains incorrect, unrecognized, corrupted or suspicious data.
Support Information: SigDict /Contents illegal data..."

I'm adding a signature from my Frontend Application using Fortify client. The documents was verify with others web sites but when i open it in Reader, i saw that message.

i upload a sample pdf

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 07, 2021 Jul 07, 2021

Copy link to clipboard

Copied

Can you name a public website that verifies the signature OK, so we can try it and compare?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 07, 2021 Jul 07, 2021

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jul 07, 2021 Jul 07, 2021

Copy link to clipboard

Copied

Your PDF including your signature is broken in a number of ways:

 

First of all a number of offsets are incorrect:

  • The startxref entry at the end claims that the cross reference table is located at position 20305. This obviously is wrong, the file is only 15446 bytes long.
  • Most entries in the incremental update cross reference table are beyond 19000, i.e. also obviously wrong.
  • The signed byte ranges are claimed to be 3304 bytes starting at offset 0 and 850 bytes starting at offset 19690; the second range again is obviously wrong.

I would assume that the signature creator originally indeed reserved a placeholder from offset 3304 to 19690 for the signature, but when injecting the signature replaced that whole placeholder by the shorter signature container.

 

Then the embedded signature container is weird as it has embedded the actual signed bytes of the PDF. This is incorrect, the embedded signature container shall not contain the signed data.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jul 07, 2021 Jul 07, 2021

Copy link to clipboard

Copied

I enlarged the placeholder again to the claimed size, and indeed the offsets are corrected, see the attached file. Adobe Reader is slightly more happy with this, at least it parses the signature container. But it in particular recognizes that the self-signed signer certificate contained in it is broken, its signature value is kaputt. Thus, it still (correctly) tells you that your signature is invalid.

It actually is a bad sign docusign that their https://validator.docusign.com/ does not show any of these errors. Thanks for demonstrating how bad that validator is.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 27, 2022 Jan 27, 2022

Copy link to clipboard

Copied

Hello, is there any sloution? My file freezes so much 😞

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jan 28, 2022 Jan 28, 2022

Copy link to clipboard

Copied

@Lana2287583331qf 

quote

Hello, is there any sloution? My file freezes so much 😞

 

As @Keshav_pki, @Ravinder5FC4, and @Red5E0F could not share example documents, there was no solution for them.

In @rossi.nicolas' case his file simply was completely broken (and apparently broken by a signing software that worked incorrectly), so the solution there was to sign using an application that does sign correctly.

As long as you don't share an example PDF that's representative for your issue, you're unlikely to find any analysis let alone solution here.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

Hi @MikelKlink , today that issue was solved. Now we are using Fortifyapp client to read token information and make the digital signature using node-signpdf libary to sign the document and we are having another problem in the process. If we try to sign a pdf that was signed previously with Acrobat for example and after that we use node-signpdf we have a diferent /type/sig section. The sign made by acrobat have a format like this:

<</Coments

Filter/Adobe.PPKLite/Type/Sig/ByteRange [0 177162 207164 1458 ]

>>

and the sign made by node-signpdf have in the first place Type/sig/byterange and after that de Comments.

We are using the addplainplaceholder of node-signpdf to make that section.

Summary, the pdf document that supposedly has two digital signature inside, just verify the last one when i open it in Acrobat reader soft.

TIA.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Dec 06, 2022 Dec 06, 2022

Copy link to clipboard

Copied

quote

Now we ... make the digital signature using node-signpdf libary to sign the document and we are having another problem in the process. If we try to sign a pdf that was signed previously with Acrobat for example and after that we use node-signpdf we have a diferent /type/sig section. ...

 

I don't really understand the issue:

  • Are the entries of your new signature dictionary in another order than those of the old signature? That would be harmless, as long as name/value pairs remain together, the order of the pairs is arbitrary.
  • Or has the dictionary of the old signature changed, too? That indeed would be bad, the whole original PDF must remain unchanged in the new one.

Unfortunately I don't know node-sign at all, so I cannot tell you how to use it. Just make sure that it adds the new signature in an incremental update of the PDF, at least if there already are signatures in the PDF.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 05, 2023 Apr 05, 2023

Copy link to clipboard

Copied

KESHAV BHAIYA ALL THE ISSUE OF TIME CONTAIN IN SINGHNATURE

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 11, 2024 Jan 11, 2024

Copy link to clipboard

Copied

Hi everyone!

I have exaxtly the same issue, and I don't know what is wrong with my PDF file. I will upload my original and final PDF's.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jan 11, 2024 Jan 11, 2024

Copy link to clipboard

Copied

There are some errors in your signed PDF:

  • The ByteRange entry is incorrect. For signatures in general the signed byte ranges should be exactly the whole signed revision except the value of the signature Contents key, and for PAdES signatures they must be - and Adobe Acrobat only accepts signatures with byte ranges of that kind. Your signed ranges are a bit off, though:
    MikelKlink_0-1704985382188.png

    ...

    MikelKlink_1-1704985464732.png

    The Contents value starts at 0x3521 = 13601 but according to your ByteRange value it should start at 13589. Similarly it ends at 0x40db = 16603 but it should end at 16591.

  • Your signed attributes are not properly DER encoded:
    MikelKlink_2-1704986080206.png

    The algorithm SHA256 is the DEFAULT value of the signingCertificateV2 attribute. Thus, it must be left out of the DER encoding.

 

(There might be more issues but these two lept to the eye.)

 

Adobe Acrobat is very sensitive in regard to the ByteRange value but probably not in regard to the DER encoding. Other validators, though, may also insist on proper DER encoding.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 11, 2024 Jan 11, 2024

Copy link to clipboard

Copied

I understand and I fix the ByteRange but is still not been verified by Adobe, I update the PDF file.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jan 11, 2024 Jan 11, 2024

Copy link to clipboard

Copied

Please take a look at the details of the signature properties:

MikelKlink_0-1705009386837.png

"The dopcument has not been modified since the signature was applied." Thus, the signature now mathematically is ok (except for the non-DER encoding of the signingCertificateV2 attribute; as mentioned above, though, Adobe is quite lax in this regard). The remaining problem is your certificate, it is not meant for creating document signatures:

MikelKlink_1-1705010202252.png

As you can see its Key usage is "Sign CRL, Sign Certificate (CA)" which are values apropriate for root or intermediate certificate authority certificates but not for end user certificates that are meant to sign documents (PDFs, e-mails, whatnots).

You may want to take a look here: If your certificate has a key usage extension, it must contain "nonRepudiation" or "digitalSignature" among its values.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 12, 2024 Jan 12, 2024

Copy link to clipboard

Copied

Thank you I've already resolved it, I will just update with the final PDF just in case it could help someone. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 12, 2024 Jan 12, 2024

Copy link to clipboard

Copied

Another question, I'm trying now to generate a multisignature by signing again the PDF, but we are using a library that when builds the incremental document it changes the references and so the original bytes (https://crates.io/crates/lopdf) in rust. Do you now any documentation or reference or library to correctly do the multisignature ?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines