v0.11-beta
"PKCS#11 not found" on a machine where the card works fine
A user installed IDPlugManager, confirmed the card was recognised by IDPlugManager itself and by other signing sites, and still got a permanent "PKCS#11 not found" in this application. They tried every library variant under the IDPlug folder and ran commands in Terminal. None of it helped, and none of it could have.
The message was simply wrong. Before touching PKCS#11 at all, the application first checked whether it could see the card reader, and that check relied on opensc-tool — a command-line utility that does not come with macOS. When it was missing, the resulting error was matched against the text not found and displayed as a PKCS#11 problem. So the application pointed at a library path that, on that code path, it never even read. Anyone who did not happen to have OpenSC installed hit this, and the setting they were sent to change had no bearing on it.
Reader detection now goes through the smart card service built into macOS. Nothing beyond IDPlugManager needs to be installed — no Homebrew, no extra package. This is what the installation instructions always promised, and now it is actually true.
Errors now say what is actually wrong
A missing card, an unresponsive card service and a genuinely unreadable PKCS#11 library used to collapse into one misleading message, and some of them were never shown at all. Each is now reported separately and in its own words, with the library-path warning appearing only when that library is really the problem.
Detection is also faster — it now answers in milliseconds instead of launching a separate process — and it can no longer hang indefinitely if the card service stops responding.
Install
Download the ZIP, unpack it and move CEI PDF Signer.app to Applications.
The first time you open it, macOS will refuse, saying it cannot verify the app is free of malware. That is expected — the app is signed ad-hoc rather than with a paid Apple certificate. To open it: double-click the app, press Done (not "Move to Trash"), then go to System Settings → Privacy & Security, scroll down to Security, and click Open Anyway next to the app name. Confirm, and enter an administrator password if asked. Every launch after that is normal.
Right-clicking and choosing "Open" was the shortcut on older macOS versions. Apple removed it, so it no longer works.
A walkthrough with screenshots is on the project page.
If you would rather confirm the download yourself rather than take that warning on trust, SHA256SUMS.txt is published beside the archive. Put both in the same folder and run shasum -a 256 -c SHA256SUMS.txt — OK means the file is byte-for-byte the one published here.