#No. Apple does not support this.

Apple's Secure Transport library does not support X.509's nameConstraints.

There is a bug in Chromium's bug database about this. And it's been closed as WontFix. Developer Ryan Sleevi had this to say on Aug 25, 2014 (archived here):

Chrome defers to the OS cryptographic stack for verification.

It's a well-known, long-standing issue that Apple does not implement name constraints. This applies to all applications that use OS X's SSL or certificate verification libraries (e.g. Safari, Curl, Python, etc)

#Related

• Should name constraints be present on a subordinate CA issued to an organization?
• Which properties of a X.509 certificate should be critical and which not?
• http://karl.kornel.us/2014/09/cas-name-constraints-and-a-business-opportunity/

#No. Apple does not support this.

Apple's Secure Transport library does not support X.509's nameConstraints.

There is a bug in Chromium's bug database about this. And it's been closed as WontFix. Developer Ryan Sleevi had this to say on Aug 25, 2014 (archived here):

Chrome defers to the OS cryptographic stack for verification.

It's a well-known, long-standing issue that Apple does not implement name constraints. This applies to all applications that use OS X's SSL or certificate verification libraries (e.g. Safari, Curl, Python, etc)

#Related

• Should name constraints be present on a subordinate CA issued to an organization?
• Which properties of a X.509 certificate should be critical and which not?
• http://karl.kornel.us/2014/09/cas-name-constraints-and-a-business-opportunity/

#No. Apple does not support this.

Apple's Secure Transport library does not support X.509's nameConstraints.

There is a bug in Chromium's bug database about this. And it's been closed as WontFix. Developer Ryan Sleevi had this to say on Aug 25, 2014 (archived here):

Chrome defers to the OS cryptographic stack for verification.

It's a well-known, long-standing issue that Apple does not implement name constraints. This applies to all applications that use OS X's SSL or certificate verification libraries (e.g. Safari, Curl, Python, etc)

#Related

• Should name constraints be present on a subordinate CA issued to an organization?
• Which properties of a X.509 certificate should be critical and which not?
• http://karl.kornel.us/2014/09/cas-name-constraints-and-a-business-opportunity/

#No. Apple does not support this.

Apple's Secure Transport library does not support X.509's nameConstraints.

There is a bug in Chromium's bug database about this. And it's been closed as WontFix. Developer Ryan Sleevi had this to say on Aug 25, 2014 (archived here):

Chrome defers to the OS cryptographic stack for verification.

It's a well-known, long-standing issue that Apple does not implement name constraints. This applies to all applications that use OS X's SSL or certificate verification libraries (e.g. Safari, Curl, Python, etc)

#Related

• Should name constraints be present on a subordinate CA issued to an organization?
• Which properties of a X.509 certificate should be critical and which not?
• http://karl.kornel.us/2014/09/cas-name-constraints-and-a-business-opportunity/