News for hackers. Stuff that matters.
Re:Maintaining digital certificate security by agl on Tuesday July 08, 2014 @01:46PM (#8005720)
Name constraints apply all the way down the chain - intermediates are implicitly limited by the constraints on their root.

CAs have been name constrained in the past, see the update here about ANSSI: http://googleonlinesecurity.blogspot.com/2013/12/further-imp...

[deleted]
Re:Maintaining digital certificate security by agl on Tuesday July 08, 2014 @01:58PM (#8005779)
A Chrome update was needed because the constraint was applied retrospectively. A name constraint is usually an X.509 extension that is included in the certificate.
[deleted]
Re:Maintaining digital certificate security by agl on Tuesday July 08, 2014 @02:29PM (#8005938)
> Every time you visit a page the OS/browser doesn't go up the entire chain of trust and check for constraints.

Oh, certainly they do. Name constraints work just like that: https://tools.ietf.org/html/rfc5280#section-4.2.1.10

So does Extended Key Usage in practice, although it's not defined that way.

There are some platforms where name constraints aren't implemented, but CAPI (Windows) certainly does implement it and I believe that NSS does also.