SmartcardServices-Users

Download

smartcardservices-users@lists.macosforge.org

January 2011

4 participants
2 discussions

Re: [SmartcardServices-Users] [Fed-Talk] Re: Require smart card login
by Shawn A. Geddis 21 Jan '11

21 Jan '11

Paul, Organizations apply policy such as requiring smart cards by managing their AD. This is not something that they would do at the client side. What is managed on the client side would be any necessary mods to support the required authentication methods (ie. manage or install client side middleware such your ADmitMac for CAC). The Mac would be bound to AD (for Authentication and Authorization) hence if AD requires ONLY Smart Cards then the Mac User would only be able to authenticate via smart cards. Whether the client system is OS X or Windows the end result is the same --- management of forced authentication methods is at the Directory Service. - Shawn _____________________________________________________ Shawn Geddis - Security Consulting Engineer - Apple Enterprise On Oct 13, 2010, at 3:24 PM, Paul Nelson wrote: > Shawn, > > How does one apply organizational policies such as "smart card required" to the Apple 10.6.3+ PKINIT solution? > > Paul > > On Oct 13, 2010, at 2:01 PM, Shawn A. Geddis wrote: > >> Before everyone claims what is and isn't the issue, we need to understand the actual setup that Souheil is using. >> >> Souheil, >> >> There are multiple methods supported for using Smart Cards for Authentication & SSO on Mac OS X 10.6. >> >> What method are you using today ? >> >> Old methods still supported: >> - PubKeyHash >> - This is a simple Hash matching between card and account >> - The user is then presented with a PIN Challenge which >> wraps/unwraps/verifies challenge - uses Private key on Card to prove ownership of card >> - uses sc_auth to update the DS with appropriate ";pubkeyhash;" and <hash> entries >> - Attribute Matching >> - This allows for selective attributes from Smart Card Login Certificate (ie. NT Principal Name) >> to be used for mapping to a single DS attribute (ie. UserPrincipalName) >> - uses /etc/cacloginconfig.plist mapping to define lookup in DS >> >> >> Mac OS X 10.6.3+ >> - PKINIT (initialization of Kerberos Session [TGT] with Auth from X.509 Cert) >> - SSO to Directory Service of choice (ie. AD) >> simplified explanation of process >> - System Bound to DS (ie. AD) >> - Utilizes NT Principal Name along with the Cert with EKU of Smart Card Login ( 1 3 6 1 4 1 311 20 2 2 ) >> --relies on /etc/cacloginconfig.plist to reference the NTPrincipalName >> - Request for Auth to KDC - acquires a TGT >> - uses PKINITMechanism configured in /etc/authorization/ for Login and ScreenSaver >> - Success: Access to HomeDir and subsequent Service Tickets >> - ... life continues ... >> >> Also, copying SmartCardServices-Users Mailing List where this discussion should be taking place >> >> - Shawn >> _____________________________________________________ >> Shawn Geddis - Security Consulting Engineer - Apple Enterprise >> >> >> On Oct 13, 2010, at 2:00 PM, Paul Nelson wrote: >>> You probably are not configured to verify the user's smart card credentials with AD. The Mac only matches the user account, and checks the certs to see if they are trusted. >>> >>> If you want true AD login with single sign-on, you could check out Thursby's ADmitMac PKI. This software obtains Kerberos credentials using a PIV card, and will configure itself using group policy so that you can enforce smart card logon that way. It also configures your system keychain with necessary certificates from Active Directory and group policy. >>> >>> Paul Nelson >>> Thursby Software Systems, Inc. >>> >>> On Oct 13, 2010, at 12:14 PM, Inati, Souheil (NIH/NIMH) [E] wrote: >>> >>>> These machines are bound to the NIH active directory and I only care about domain users for now. I haven't had to use sc_auth, the AD lookup based on the card credentials has been working fine. >>>> >>>> >>>> On Oct 13, 2010, at 12:51 PM, Qureshi, Usman wrote: >>>> >>>>> Have you tried using the sc_auth command? Is the user a domain user or a >>>>> local user? >>>>> >>>>> -----Original Message----- >>>>> From: fed-talk-bounces+usman.qureshi=unisys.com(a)lists.apple.com >>>>> [mailto:fed-talk-bounces+usman.qureshi=unisys.com@lists.apple.com] On Behalf >>>>> Of Inati, Souheil (NIH/NIMH) [E] >>>>> Sent: Wednesday, October 13, 2010 12:15 PM >>>>> To: fed-talk(a)lists.apple.com >>>>> Subject: [Fed-Talk] Require smart card login >>>>> >>>>> Hi all, >>>>> >>>>> Does anyone know the right way to set up /etc/authorization so that users >>>>> are REQUIRED to use a smart card? >>>>> A Snow Leopard 10.6 only solution is sufficient. >>>>> >>>>> Thanks, >>>>> Souheil

7 9

FW: [Fed-Talk] PKI Certificate ³Name Constraints² extension treated as an unknown critical extension
by Dan O'Donnell 03 Jan '11

03 Jan '11

Cross-posted as relevant to Smart Card Services from Apple Fed-talk. ------ Forwarded Message From: "Disiena, Ridley J. (GRC-VO00)[DB Consulting Group, Inc.]" <obscured> Date: Mon, 3 Jan 2011 14:34:52 -0600 To: "fed-talk(a)lists.apple.com" <fed-talk(a)lists.apple.com> Subject: [Fed-Talk] PKI Certificate ³Name Constraints² extension treated as an unknown critical extension Issue: OS X 10.5.x & 10.6.x treats the ³Name Constraints² extension as an unknown critical extension and therefore treats the certificate as invalid due to "unrecognized critical extension". I know there are previous threads on this subject for current live certificates of particular agencies and DoD and we know that this issue is because OS X does not recognize the extension yet. I'm bringing this back up on the list because due this issue is likely to plague Federal OS X users and their customers for the foreseeable future until resolved by Apple since several proposed new Federal Bridge Certificates will likely have such a critical extension. This is news to me since the last posting on the subject, I had hoped newly issues certificates would not be effected but at this time that appears that will not be the case. Complications: Since the effected Federal Bridge cross certificates will be found in the PKCS#7 bundles found via validation of AIA locations of Federal Agency certificates, applications that use OS X¹s certificate security functionality including the OS X operating system itself, will treat certificates that are valid, falsely as invalid due to very outdated libraries. As mentioned in a previous post, the openSSL library has been updated to recognize and use the Critical Name Extension as of 0.9.8 released 5 years ago, and the PKI definition of the ³Name Constraints² extension is now 12 years old. If this is the case, this is not an issue with the certificates, it is a case of severely out dated PKI libraries in OS X. I have put in a bug report [which will likely get sent back as duplicate and closed] and am following up with Enterprise Support but since this issue has been occurring for 2 OS versions already with no response from Apple on related posts, I wanted to make the other Federal folks involved with PKI aware, that at this time, it appears we will be effected for the foreseeable future, until Apple addresses the issue. FPKI is being made aware of the issue but in looking at how long ago these extensions were defined in best practices documentation, it looks like the issue is on the Apple side, with OS X failing to recognize / utilize recent libraries, and not so recent standards. Related Fed-Talk Posts: Related name constraints noted on Fed-Talk April 2010 PKI Certificates - Unknown Critical Extensions causing problems... http://lists.apple.com/archives/fed-talk/2010/Apr/msg00005.html http://lists.apple.com/archives/fed-talk/2010/Apr/msg00006.html ³Also, it looks like the *key* security binaries and/or Frameworks are *STATICALLY* linked to the 'old' OpenSSL libraries² Related name constraints noted on Fed-Talk December 2010 http://lists.apple.com/archives/fed-talk/2010/Apr/msg00008.html http://lists.apple.com/archives/fed-talk/2010/Nov/msg00177.html Related policy constraints noted on Fed-Talk October 2009 http://lists.apple.com/archives/apple-cdsa/2009/Oct/msg00002.html Backup Information: OpenSSL 0.9.8 released Tue, 05 Jul 2005 [ Over 5 years ago ] http://www.mail-archive.com/openssl-announce@openssl.org/msg00063.html ---> * Added support for certificate policy mappings, policy constraints and name constraints. <--- IETF Document Definition of ³Name Constraints² extension: January 1999 [12 Years ago] http://www.ietf.org/rfc/rfc2459.txt Housley, et. al. Standards Track [Page 34] RFC 2459 Internet X.509 Public Key Infrastructure January 1999 ---> 4.2.1.11 Name Constraints ------ End of Forwarded Message __________________________________________________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

1 0