On Wed, Jan 10, 2007, Andrews, Rick wrote: > We're trying to do client auth to an Apache web server, and we've > discovered that if the end entity cert's issuing CA cert has an > extendedKeyUsage extension, but the extension doesn't contain the > clientAuth and serverAuth values, then the SSL handshake fails with an > invalid CA error. Adding those values, or removing the extendedKeyUsage > extension from the issuing CA cert allows it to work. > > This seems like a bug to some of us around here. The end entity cert > should definitely have clientAuth and serverAuth, but we don't believe > the issuing CA cert needs to have them too. > > Has anyone heard of this? I will submit it as a bug, but I wanted to > check with the list first. Thanks, >
Well if EKU is being placed in a CA certificate I'm assuming there is some reason for it as opposed to the extension being ignored. Is the anyExtendedKeyUsage keyPurposeID present too? OpenSSL doesn't currently interpret that which is a bug. If the letter of RFC3280 is being applied strictly then the presence of EKU along with serverAuth and clientAuth (and no other values) would imply that the key can only be used for serverAuth and clientAuth purposes. That could be interpreted as meaning that it isn't even a valid CA certificate. The interpretaion OpenSSL uses is not that strict but conforms with other software for example MSIE. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
