April 2015 - SmartcardServices-Users

Re: [SmartcardServices-Users] [Fed-Talk] CAC-enabled login OS X10.7 & 10.8
by Shawn Geddis 02 Nov '16

02 Nov '16

Michael, All Smart Card related questions should be communicated on Apple's SmartCardServices Project Lists over at MacOSForge.org. A brief debunking of misinformation previously shared on this thread... There are three methods for associating a Smart Card to a given user account in either the local or remote DS. PubKey Hash - Default method used by OS X and requires sc_auth Attribute Matching - requires /etc/cacloginconfig.plist PKINIT - requires /etc/cacloginconfig.plist and Mac bound to a KDC All methods require that the smartcard-sniffer line be present in /etc/authorization for catching the Smart Card and gathering the PIN for the associated Challenge Response with the card for use of the Private Key on the card. Tokend modules no longer ship with OS X (as of OS X Lion), but are freely available for 10.7, 10.8 from Apple's SmartCardServices project at MacOSForge. This is why nothing happens when you insert a reader / card on a vanilla install of OS X Lion or higher. ALL other components of SmartCard Services are present and have even been updated in released versions of OS X since OS X Lion v10.7.0. Project Site: http://smartcardservices.macosforge.org/ Installers: http://smartcardservices.macosforge.org/trac/wiki/installers There are also third-party commercially supported solutions from, for example, Centrify, charismathics and Thursby. ".....Comparing against 10.4 references these seem to indicate that smart card login is already enabled, besides the name change from smartcard-sniffer to PKINITMechanism...." No, "smartcard-sniffer" is NOT a name change for PKINITMechanism. "smartcard-sniffer" performs a swap of the login window (dynamically) and captures PIN "PKINITMechanism" performs the Apple provided PKINIT services for Login Authentication. "...Unfortunately Apple dropped support and now it is a requirement in many places, all places that supply Windows-software for this but if you use OS X you have to find your own solution..." You have the SAME functionality still offered via my installers from Apple's MacOSForge Project You have multiple commercial solutions as well as noted above: Centrify, charismathics and Thursby. Please register and redirect ALL Smart Card related questions to one of the appropriate Mailing list on MacOSForge. http://lists.macosforge.org/mailman/listinfo Smart Card Users: https://lists.macosforge.org/mailman/listinfo/smartcardservices-users Smart Card Developers: https://lists.macosforge.org/mailman/listinfo/smartcardservices-dev - Shawn ______________________________________________________ Shawn Geddis geddis(a)me.com Enterprise Security Consulting Engineer, Apple geddis(a)apple.com MacOSForge: Smart Card Services Project Lead: Web: http://smartcardservices.macosforge.org/ Lists: http://lists.macosforge.org/mailman/listinfo ______________________________________________________ On Feb 19, 2013, at 1:40 PM, Michael Kluskens <mklus(a)ieee.org> wrote: > I'm well aware of the sc_auth command and on previous versions of OS X I had CAC login enabled. However, in testing an OS X Lion and an OS X Mt. Lion system, inserting the CAC card has no effect. Both systems otherwise have full CAC functionality and I used the Identity Private Key. > > I have not yet tried this on a clean system with no security configuration (disabling suid's binaries, etc.) so it is possible that both systems have been broken with regards to CAC login. > > I was hoping someone could actually confirm what setup works on OS X 10.7 & 10.8 because at present the discussed information has not worked for me. > > Looking at /etc/authorization under system.login I see: > > builtin:policy-banner > loginwindow:login > builtin:reset-password,privileged > builtin:forward-login,privileged > builtin:auto-login,privileged > builtin:authenticate,privileged > PKINITMechanism:auth,privileged > loginwindow:success > HomeDirMechanism:login,privileged > HomeDirMechanism:status > MCXMechanism:login > loginwindow:done > > and under authenticate I see: > > builtin:authenticate > builtin:reset-password,privileged > builtin:authenticate,privileged > PKINITMechanism:auth,privileged > > Comparing against 10.4 references these seem to indicate that smart card login is already enabled, besides the name change from smartcard-sniffer to PKINITMechanism. > > Michael > >> From: "Danberry, Michael J Mr ARMY GUEST USA" <michael.danberry(a)us.army.mil> >> The specific location for this information is at: http://militarycac.com/errors2.htm#OTHER_QUESTIONS. Question 2 > >> From: "Bomar, Matt W ERDC-RDE-ITL-MS Contractor" <Matthew.W.Bomar(a)erdc.dren.mil> >> >> Have you looked at the "sc_auth" command? It should allow you to associate >> a certificate with a local user account for CAC login. It's still present >> in 10.8. >> >> On 2/14/13 4:30 PM, "Michael Kluskens" <mklus(a)ieee.org> wrote: >> >>> What are the choices for CAC enabled login on OS X 10.7 & 10.8. >>> >>> I'm looking at OS X systems which may not have access to a MS Domain >>> Server, i.e. isolated network. Some would have access and some would not >>> have access all the time. >>> >>> I thought maybe some changes to /etc/authorization might reenable >>> CAC-login but I haven't started an attempt yet. >>> >>> Unfortunately Apple dropped support and now it is a requirement in many >>> places, all places that supply Windows-software for this but if you use >>> OS X you have to find your own solution.

2 1

Re: [SmartcardServices-Users] OS X 10.9 (10.10) Smart Card Logon But No PKINIT
by Hoit, Daniel S. 24 Apr '15

24 Apr '15

Thanks Dan. I may look into that then. --DH On Apr 24, 2015, at 8:48 AM, "Brodjieski, Daniel D CTR WHS EITSD (US)" <daniel.d.brodjieski.ctr(a)mail.mil> wrote: > Hi Daniel- > I have had similar issues when trying to leverage the built-in kerberos > tools with Mavericks and Yosemite. I have had luck when I download and > install the Heimdal tools directly from the project site(if I recall, it’s > version 1.5). I know the files haven’t been updated since last October, > but it was the only way I could get a kerberos ticket using the command > line. After installing it into /usr/heimdal, I’m able to run: > > /usr/heimdal/bin/kinit -C KEYCHAIN: -D KEYCHAIN: --pk-enterprise > > > And this has been working for us. > > Hope that’s helpful. > > Respectfully, > > Dan Brodjieski > > > > On 4/23/15, 4:36 PM, "Hoit, Daniel S." <hoit2(a)llnl.gov> wrote: > >> Hate to drag up stuff from the past, but I wonder if this was ever >> figured out? >> I'm looking at the same basic situation. I can do cacloginconfig based >> smart card login under 10.10.3, but I don't get a kerberos TGT for the >> user, and no options that I toss at kinit seem to enable it to do a >> pkinit. >> >> Here is what I have: >> Gemalto smart card, being correctly recognized and read by the system. I >> can see the "keychain", the certificate on board has the correct eku for >> smart card login, and it shows as trusted. Root certificates for AD are >> installed. Cacloginconfig.plist points to the right attributes. I can go >> to the login window, insert the card, put in my pin, and login, but no >> kerberos ticket is generated. >> >> If I run kinit -C KEYCHAIN: -D KEYCHAIN: --windows --pk-enterprise >> I get the result: kinit: krb5_pk_enterprise_certs: Failed to find PKINIT >> certificate: Certificate not found >> Thinking that maybe this is a search path issue, and those trailing : >> after KEYCHAIN seems to indicate its some sort of path separator, I tried >> the following: >> >> Run security list-keychains. Copy "smart card keychain" name. >> run kinit -C KEYCHAIN:"smart card keychain name" -D KEYCHAIN: --windows >> --pk-enterprise >> Result: kinit: krb5_pk_enterprise_certs: PK-INIT cert didn't contain >> principal SAN >> >> Now, the certificate I'm trying to use DOES have a SAN, so I don't know >> if this is further confusing things, or helping and showing the next >> error in the chain. >> >> I think I've tried every possible combination of documented switches in >> kinit, but I can't seem to get any further. >> Does anyone have any suggestions? >> >> --DH >> >> >> On May 22, 2014, at 7:59 AM, "Brown, Alexander [USA]" >> <Brown_Alexander2(a)bah.com> wrote: >> >>> I exported the public certificate to a file and then ran "sudo security >>> verify-cert -p pkinitClient -c <certificate-file>" (replacing >>> <certificate-file> with the actual file name) and the message I received >>> was "certificate verification successful". >>> >>> >>> Alex >>> >>> -----Original Message----- >>> From: Henry B Hotz [mailto:hbhotz@oxy.edu] >>> Sent: Tuesday, May 20, 2014 5:02 PM >>> To: Yoann Gini >>> Cc: Brown, Alexander [USA]; smartcardservices-users(a)lists.macosforge.org >>> Subject: [External] Re: [SmartcardServices-Users] OS X 10.9 Smart Card >>> Logon But No PKINIT >>> >>> Just for completeness we should mention the command "security >>> verify-cert -p pkinitClient". I don't think it calls any Heimdal >>> Kerberos code, but it should tell you something about what the Apple PKI >>> code thinks. >>> >>> On May 20, 2014, at 12:11 AM, Yoann Gini <yoann.gini(a)gmail.com> wrote: >>> >>>> Le 19 mai 2014 à 22:31, Henry B Hotz <hbhotz(a)oxy.edu> a écrit : >>>> >>>>> On May 16, 2014, at 3:23 PM, Yoann Gini <yoann.gini(a)gmail.com> wrote: >>>>> >>>>>>> I got the error "kinit: krb5_pk_enterprise_certs: Failed to find >>>>>>> PKINIT certificate: Certificate not found". The smart card I am >>>>>>> using for this is the DoD CAC. >>>>>> >>>>>> I've got this problem too. I've found (via reverse engineering) that >>>>>> the Kerberos framework has some problems in the algo used to validate >>>>>> the certificate on the card. It seems to see it but don't take it as >>>>>> valid. >>>>> >>>>> Alexander's cert ought to be OK since it's at least recognized, but >>>>> I've seen a similar apparent mis-match in processing the KDC reply >>>>> from a Heimdal KDC. I suspect the problem is a mis-match between >>>>> Apple's PKI framework and Heimdal. >>>> >>>> Yes, this can also be an explanation for what I've seen. >>>> >>>> When I've said « it don't take it as valid », I was talking about the >>>> whole checkup process. Certificate validity and authorized usage. >>>> >>>> Of course I've try different KU and EKU without any success. >>> >>> At least for Heimdal, I think KU of digitalSignature is all that's >>> required. I wonder if it's worth trying Heimdal on a Linux system for >>> comparison? (I suggest Debian with the OpenSC card drivers if someone >>> wants to try.) If nothing else the error messages might be clearer, and >>> you could write a better bug report for Apple. >>> >>> Personal email. hbhotz(a)oxy.edu >>> >>> >>> >>> _______________________________________________ >>> SmartcardServices-Users mailing list >>> SmartcardServices-Users(a)lists.macosforge.org >>> https://lists.macosforge.org/mailman/listinfo/smartcardservices-users >> >> _______________________________________________ >> SmartcardServices-Users mailing list >> SmartcardServices-Users(a)lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/smartcardservices-users

1 0

OS X 10.9 Smart Card Logon But No PKINIT
by Brown, Alexander [USA] 23 Apr '15

23 Apr '15

Hello, I have smart card logon working with Mac OS X 10.9 to a Windows Active Directory domain by using cacloginconfig.plist and mapping based on the NT Principal Name. So this is working ok but when I took a look at the traffic between the Mac and the Windows domain I noticed there wasn't any Kerberos traffic and PKINIT isn't being used. Does anyone have PKINIT working with OS X 10.9 and if so can you share some steps on how that is configured? When I have my smart card in and run "kinit -C KEYCHAIN: -D KEYCHAIN: --windows --pk-enterprise" I got the error "kinit: krb5_pk_enterprise_certs: Failed to find PKINIT certificate: Certificate not found". The smart card I am using for this is the DoD CAC. Also one other question, does anyone know if any certificate revocation checking takes place on the Mac during smart card logon? Alex Brown Associate Booz | Allen | Hamilton ________________________________ brown_alexander2(a)bah.com<mailto:brown_alexander2@bah.com>

4 8