Anyone else see smartcard use causing eventual authentication failure?
We've had several users who have noticed that using a smart card on their system eventually causes authentication services to go out to lunch. Thus, when you click the lock icon in any App, you get nothing. No prompt, no unlock, just nothing. Rebooting fixes the issue, as does doing a kill -9 of securityd. This appears to happen on both 10.7 and 10.8 whether the smart card itself is being used by the Mac, or passed through to a windows VM. I'd like to file a bug on it, but duplicating the issue has been difficult up till now. I've seen it personally on my own machines, as well as getting reports of it from the field, but it seemed to be intermittent. I've discovered on at least one of my machine though that I can trigger the condition by unlocking the smart card in keychain access. Is this a known issue? Anyone else seeing this? Thanks, --DH
I can reproduce this problem every single time I log into something using my smart card, and I use PKard. The only way for me to fix it is to kill the securityd. I do it with Activity Monitor instead of the CLI. It is documented on a message board for Thursby Software as well. I called Apple about it and they didn't offer much help. I think a bug report would be great. Matthew On Nov 1, 2012, at 2:29 PM, "Hoit, Daniel S." <hoit2@llnl.gov> wrote:
We've had several users who have noticed that using a smart card on their system eventually causes authentication services to go out to lunch. Thus, when you click the lock icon in any App, you get nothing. No prompt, no unlock, just nothing. Rebooting fixes the issue, as does doing a kill -9 of securityd. This appears to happen on both 10.7 and 10.8 whether the smart card itself is being used by the Mac, or passed through to a windows VM.
I'd like to file a bug on it, but duplicating the issue has been difficult up till now. I've seen it personally on my own machines, as well as getting reports of it from the field, but it seemed to be intermittent. I've discovered on at least one of my machine though that I can trigger the condition by unlocking the smart card in keychain access.
Is this a known issue? Anyone else seeing this?
Thanks, --DH
_______________________________________________ SmartcardServices-Users mailing list SmartcardServices-Users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/smartcardservices-users
I've shared this report to Thursby support. +1 (817) 478-5070 or support@thursby.com If it's in our software, we'll work on it. If it's in OS X, we'll make sure it's a RADAR, if we haven't already. Regards, Simon @Thursby On Nov 1, 2012, at 1:40 PM, Matthew Smith <mls14@mac.com> wrote: I can reproduce this problem every single time I log into something using my smart card, and I use PKard. The only way for me to fix it is to kill the securityd. I do it with Activity Monitor instead of the CLI. It is documented on a message board for Thursby Software as well. I called Apple about it and they didn't offer much help. I think a bug report would be great. Matthew On Nov 1, 2012, at 2:29 PM, "Hoit, Daniel S." <hoit2@llnl.gov> wrote:
We've had several users who have noticed that using a smart card on their system eventually causes authentication services to go out to lunch. Thus, when you click the lock icon in any App, you get nothing. No prompt, no unlock, just nothing. Rebooting fixes the issue, as does doing a kill -9 of securityd. This appears to happen on both 10.7 and 10.8 whether the smart card itself is being used by the Mac, or passed through to a windows VM.
I'd like to file a bug on it, but duplicating the issue has been difficult up till now. I've seen it personally on my own machines, as well as getting reports of it from the field, but it seemed to be intermittent. I've discovered on at least one of my machine though that I can trigger the condition by unlocking the smart card in keychain access.
Is this a known issue? Anyone else seeing this?
Thanks, --DH
_______________________________________________ SmartcardServices-Users mailing list SmartcardServices-Users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/smartcardservices-users
_______________________________________________ SmartcardServices-Users mailing list SmartcardServices-Users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/smartcardservices-users
Mr. Hoit, This happens all the time in 10.7 and 10.8 and there is a bug filed already 9842441. You should file a bug anyway even though they'll close it as a duplicate. They keep track of that. If they see more than N people make a stink, it goes to a higher priority to fix. -- John Lamb Desktop Support Technician [Contractor] Customer Support Branch Center for Biomedical Informatics (CBI) National Heart Lung and Blood Institute, NIH 10 Center Drive - Building 10 6C103 Bethesda, MD 20892-7994 Telephone (240) 751-6562 | Email: John.Lamb2@nih.gov | NHLBI Computer Services: http://insider.nhlbi.nih.gov/computer On 11/1/12 2:29 PM, "Hoit, Daniel S." <hoit2@llnl.gov> wrote:
We've had several users who have noticed that using a smart card on their system eventually causes authentication services to go out to lunch. Thus, when you click the lock icon in any App, you get nothing. No prompt, no unlock, just nothing. Rebooting fixes the issue, as does doing a kill -9 of securityd. This appears to happen on both 10.7 and 10.8 whether the smart card itself is being used by the Mac, or passed through to a windows VM.
I'd like to file a bug on it, but duplicating the issue has been difficult up till now. I've seen it personally on my own machines, as well as getting reports of it from the field, but it seemed to be intermittent. I've discovered on at least one of my machine though that I can trigger the condition by unlocking the smart card in keychain access.
Is this a known issue? Anyone else seeing this?
Thanks, --DH
_______________________________________________ SmartcardServices-Users mailing list SmartcardServices-Users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/smartcardservices-users
participants (4)
-
Hoit, Daniel S.
-
Lamb, John (NIH/NHLBI) [C]
-
Matthew Smith
-
Simon Hartley