[
https://issues.apache.org/jira/browse/PDFBOX-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184474#comment-14184474
]
Andreas Lehmkühler commented on PDFBOX-2458:
--------------------------------------------
David provides a fix, too.
{quote}
Should anybody care, David at BC found the bug that managed to work for prior
BC versions, but no longer does under 1.51. We changed to this method in
CMSTypedDataInputStream to return 'in' instead of 'null' and it works under
1.50 as well as 1.51:
@Override
public Object getContent()
{
return in;
}
{quote}
As his own code is similar to ours, I'm going to apply the fix too.
> Signing doesn't work anymore using BC 1.51 instead of 1.50
> ----------------------------------------------------------
>
> Key: PDFBOX-2458
> URL: https://issues.apache.org/jira/browse/PDFBOX-2458
> Project: PDFBox
> Issue Type: Bug
> Components: Signing
> Affects Versions: 1.8.7, 2.0.0
> Reporter: Andreas Lehmkühler
> Assignee: Andreas Lehmkühler
> Fix For: 1.8.8, 2.0.0
>
>
> Due to a report of David Wall on users@ signing no longer works using BC 1.51
> instead of 1.50.
> {quote}
> I'm now getting an invalid digital signature that I created on PDFs we
> generate (via wkhtmltopdf and PDFBox 1.8.7). It says "At least one signature
> is invalid" but I previously could create them with valid signatures. This
> occurred when going from BouncyCastle 1.50 to 1.51, and if I go back to 1.50,
> it works fine.
> The invalid signature complains that the "Document has been altered or
> corrupted since it was signed".
> Here's a link to an existing PDF that has an invalid signature:
> http://open.esignforms.com/pdfboxlist/MyDocumentsGOOD.pdf (using BC 1.50)
> http://open.esignforms.com/pdfboxlist/MyDocumentsBAD.pdf (using BC 1.51)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
