Note: this update is specific to CACkey driver users. Please give it a run and let us know if it works for you. It is already available for Download from here: Index of /download/0.7.8 Kenneth has just released a new version 0.7.8 of the CACkey driver that should solve this issue and includes several fixes. We have been working closely with Apple and especially with Kenneth Van Alstyne, the developer who manages the Mac OSX port of the open source CACkey driver, to understand and solve this issue. I will provide some technical details at the end if you’re interested, but first we have some important news.
I did, and you can see the results on the screenshots above.ĭear CAC and PIV card users on MacOS computers, here’s an update on our progress to solve the issue that many of you are facing when signing in Adobe Acrobat and Reader after updating Mac OSX to version 10.11.6 or 10.12. Now it correctly uses what it's supposed to - SHA256:įor those people who have problems with PDF digital signature - please check what tokend you're using, and try with a working one instead.
#Cac reader for mac high sierra mac os x
Mac OS X 10.11.6 improved PDF signing - before Acrobat was only using SHA1 if the signing key was on a CAC. I did not have to attach a PKCS#11 library, as it is unnecessary when your tokend is good: These tools fully support my workflow for smartcards, including PDF signing, S/MIME (signature and encryption, using Apple Mail and MS Outlook 20), Web sites authentication (Apple Safari, Google Chrome, Firefox using PKCS#11 library opens-pkcs11.so), and smartcard-based computer logon. If you do not have a working tokend - then the workaround provided above (adding a PKCS#11 library that accesses the CAC directly) would solve the problem, assuming your PKCS#11 library works correctly.Ĭurrently I'm using Open Source tools ( OpenSC and OpenSC.tokend). For it to work out of box you need a working tokend. PDF signing using smart card (CAC or PIV) works fine on Mac OS X 10.11.6.
0 kommentar(er)
