Uploaded image for project: 'PDFBox'
  1. PDFBox
  2. PDFBOX-2458

Signing doesn't work anymore using BC 1.51 instead of 1.50

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.7, 2.0.0
    • Fix Version/s: 1.8.8, 2.0.0
    • Component/s: Signing
    • Labels:
      None

      Description

      Due to a report of David Wall on users@ signing no longer works using BC 1.51 instead of 1.50.

      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)

        Attachments

          Activity

            People

            • Assignee:
              lehmi Andreas Lehmkühler
              Reporter:
              lehmi Andreas Lehmkühler
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: