Card support stopped workin on macOS in 2019.1 (reason: false positive in Cylance AV software, workaround: whitelist file)
I upgraded to 2019.1 and after this all attemps to use my YubiKey stopped working.
gpg --card-stats would just produce an error message about scdeamon not being found. I tried completely removing gpgtools and installing again with the same outcome.
In the end I downgraded to 2018.5 which works fine.
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
Support Staff 1 Posted by Luke Le on 26 Aug, 2019 09:31 AM
we are very sorry for the bad expierience.
Would you be able to send us the exact error message? Our own smart cards seem to work fine with 2019.1 so any additional debugging information would be of great help.
2 Posted by Hugo Tunius on 26 Aug, 2019 09:58 AM
this is what I saw
Support Staff 3 Posted by Luke Le on 26 Aug, 2019 10:19 AM
Could you also run the following commands:
4 Posted by Hugo Tunius on 26 Aug, 2019 10:23 AM
I don't have 2019.1 installed anymore, but gpg was in
/usr/local/bin/gpgwhen I checked. I assumed it was symlinked to
Support Staff 5 Posted by Luke Le on 26 Aug, 2019 10:45 AM
Sometimes these errors are seen if another gpg (from homebrew/macports/fink) is installed along side.
Could you have a look if you find a crash log in
Maybe scdaemon is crashing for a reason.
6 Posted by Hugo Tunius on 26 Aug, 2019 01:28 PM
Yup you were right, it was crashing.
Support Staff 7 Posted by Luke Le on 26 Aug, 2019 02:29 PM
Are you using Cylance by any chance or some antivirus? Someone mentioned that the libksba file was identified as problematic. We have not received details yet however.
8 Posted by Hugo Tunius on 30 Aug, 2019 08:14 AM
Yup this was my work machine which does use Cylance. That was my first thought too, but I didn't see anything in the logs of Cylance. I'll try on my personal machine which does not have Cylance to verify.
9 Posted by Hugo Tunius on 30 Aug, 2019 09:40 AM
I checked and it worked on my personal machine. I also found an entry in Cylance about removing that dylib so you are correct the issue was with Cylance.
10 Posted by Hugo Tunius on 30 Aug, 2019 11:10 AM
Just confirming that after whitelisting the dylib in Cylance it all works. Thanks for your help Luke
Support Staff 11 Posted by Luke Le on 30 Aug, 2019 11:20 AM
Perfect thank you very much for your update!
The people at Cylance told us that they are using AI for their detection heuristic and it appears to have been off in this case.
Steve closed this discussion on 01 Sep, 2019 04:48 PM.