*.fedoraproject.org

[Mike McGrath]

We now have a *.fedoraproject.org wildcard cert.  This will make creating
websites significantly easier.  We already have some plans for the
translated wiki and such.  I'm going to be implementing this cert soon for
much of our infrastructure.  My tests worked fine but just the same,
conversion to production might produce some cert oddness.  Please do keep
your eyes open.

I've never worked with a wildcard cert before and right now plain old
"fedoraproject.org" doesn't work.  This makes sense but I'm wondering
if
anyone knows a way around it.  Is it not possible to create a cert for
your entire domain as you'll always have at least a *.example.com and a
root "example.com" cert?  correct me if I'm wrong on that.

	-Mike

[Till Maas]

On Mon August 11 2008, Mike McGrath wrote:
>  We now have a *.fedoraproject.org wildcard cert.  This will make
> creating 
Yippie, this is superp.

>  I've never worked with a wildcard cert before and right now plain
> old
>  "fedoraproject.org" doesn't work.  This makes sense but I'm wondering
> if
>  anyone knows a way around it.  Is it not possible to create a cert for
>  your entire domain as you'll always have at least a *.example.com and a
>  root "example.com" cert?  correct me if I'm wrong on that. 
The best documentation I know is this, but I did not search for it recently:

https://wiki.cacert.org/wiki/VhostTaskForce

Regards,
Till

[Eric Brown]

Mike McGrath wrote:
>  We now have a *.fedoraproject.org wildcard cert.  This will make
> creating
>  websites significantly easier.  We already have some plans for the
>  translated wiki and such.  I'm going to be implementing this cert soon for
>  much of our infrastructure.  My tests worked fine but just the same,
>  conversion to production might produce some cert oddness.  Please do keep
>  your eyes open.
>  
>  I've never worked with a wildcard cert before and right now plain old
>  "fedoraproject.org" doesn't work.  This makes sense but I'm wondering
> if
>  anyone knows a way around it.  Is it not possible to create a cert for
>  your entire domain as you'll always have at least a *.example.com and a
>  root "example.com" cert?  correct me if I'm wrong on that. 
You are correct.  You must have the *.domain CERT *and* the root
domain CERT.  No way around it.

-- 
Eric Brown | Manager, Information Services | Red Hat, Inc.
(o) +1.404.442.2033 (c) +1.404.964.6062 | Key ID: 0xA092F823
GPG: B8E5 9D48 5ECC 09BD 160E  4698 52EC 3DCB A092 F823