v0.10-beta

Documents that could not be signed at all

Some PDFs failed with "No key available to decrypt, please authenticate first" and could not be signed. Fixes issue #1.

Those documents are encrypted. What made this confusing is that they open in any viewer without asking for anything, so there is no sign that they are protected. Insurers, banks and public institutions commonly apply an owner password to restrict printing or copying while leaving the opening password empty. The file is still encrypted underneath, and the application was not unlocking it before reading.

It now unlocks such documents automatically, so they sign like any other file. A PDF that genuinely requires a password to open still cannot be signed directly, but it now says so clearly and tells you what to do, instead of failing with a technical message.

Two more problems found behind that one

Both were only reachable on encrypted documents.

Signature placement failed on them, so even once a document was unlocked the signature was never drawn.

More seriously, the protection that stops the application from stamping over a document that is already signed had quietly stopped working on encrypted files. It could have modified an already signed document and invalidated that signature. This never produced an error message, so it would not have been reported.

Install

Download the ZIP, unpack it, move CEI PDF Signer.app to Applications, then right click the app and choose Open the first time.

Verify the download if you wish:

shasum -a 256 CEI-PDF-Signer-v0.10-beta-macOS.zip

The expected value is in SHA256SUMS.txt.

Recent releases

v0.9-beta fixed Romanian diacritics in the visible signature. v0.8-beta fixed the packaging fault that stopped the application opening at all. If you are coming from v0.7-beta or earlier, read those notes too.