Re: Wildcard certificate

On 4/6/2016 11:23 PM, Scott Klement wrote:

> It seems to me that certificates aren't that expensive. I'd just get
> one for each domain name.
>
> -SK
>

True enough they are pretty cheap, but here's where we're running into issues more and more. Datacetners are starting to demand that ALL devices be those servers, web pages, firewalls, network switches, fiber switches, tape drives, tape libraries, SANs, HMCs (and the beat goes on) ALL have signed certificates. They are stating this is for 'compliance' as demanded by other residents of the DC.

Having to acquire and separately install all those certs WILL be expensive and will absolutely become land mines all through the DC. Some point 1 year or two from now you'll need to access some device and 'bang' goes the landmine as you discover the cert is expired.

At lease with a wildcard you can say: "OK On June 1 every year we roll through every single device and updated the cert because it expires on July 1." Still a pain in the backside but it's one ticket to ride for ALL equipment.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/6/2016 9:58 AM, Rob Berendt wrote:

We are switching over some of our sites from names like
dekkocustomers.com, dekkosuppliers.com and so on to names like
customers.dekko.com suppliers.dekko.com.
One goal is to be able to use one certificate for all.

When I view the certificate via FF I see:

Website: customers.dekko.com
Issued To
Common Name (CN) *.dekko.com
Organization (O) Group Dekko, Inc
Organizational Unit (OU) <Not Part Of Certificate>

Our external scanning service does an nslookup on the IP address
associated with that website and it returns customers.dekko.com (as it
should). It then compares that to the certificate and says that
customers.dekko.com doesn't match *.dekko.com.

One could argue that the scanning service needs to figure this out. I
haven't got a year to spare on this.

If I just get another certificate and just leave the CN dekko.com instead
of *.dekko.com will this work (as a general rule)?


Rob Berendt