[Date Prev][Date Next]
Re: OpenLDAP and wildcard SSL certs
--On Thursday, April 14, 2005 6:18 PM -0700 Howard Chu <email@example.com>
Brent J. Nordquist wrote:
As far as I know, CN should be the fully qualified domain
name. subjectAltName should have the wildcard.
But that defeats the whole purpose. Then you'd have to have one cert.
for each FQDN and then what's the point of using a wildcard at all?
Or am I misunderstanding what you're saying?
I should note that there was never a 2.1.32 OpenLDAP release, 2.1.30 was
the last. And since 2.1 is Historic and no longer supported, there's not
much point in pursuing this further until you upgrade to a supported
release (like 2.2.24). Likewise, OpenSSL 0.9.6b is ancient, and known to
have a number of security vulnerabilities. It is not a good idea to use
any of this old software. The wildcard features are known to work
correctly in recent releases.
As noted in the original message you referenced, RFC2459 does not permit
the use of wildcards in the subject DN of a cert. The specification only
allows wildcards to be used in the subjectAltName extension. Any
organizations and software packages supporting wildcards in the subject
DN are broken, and cannot be considered to have a reliable security
SSL and certificates are not just some Magic Security Solution that can
be used arbitrarily without any thought. It is important to understand
exactly what these things are for. A certificate *certifies* that an
entity is exactly who it claims to be. As such, a certificate with a
wildcarded subject DN is pure nonsense - "hello, my name is <every
possible entity of Example.COM>". The use of wildcards in the
subjectAltName also have a very clear meaning. When presenting such a
cert, the entity is saying "Hello, my name is server1.example.com AND I
can accept requests on behalf of other servers in example.com." Again,
the point of a certificate is to uniquely and unambiguously identify
something, because you cannot make any conclusions about the integrity of
a transaction if you cannot unambiguously identify who you're transacting
with. Without such an assurance, there is no security, and you may as
well not bother using certificates at all.
All of this aside, I'll note that I submitted a patch to the OpenLDAP 2.2
branch that was incorporated, and allows you to use a wildcard cert with
the wildcard in the subject DN of the cert, since I can't find a single
cert vendor that actually follows RFC2459, and all other software products
I've used with wildcard certs in the subject DN worked just fine with them.
So if you will follow the advice to upgrade to OL 2.2.24, your wildcard
cert should work just fine, as I'm using a wildcard cert with my Stanford
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin