Re: Wildcard certificate

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I think you need a new scanning service.

One that understands wildcard certs.

Charles

On Wed, Apr 6, 2016 at 10:58 AM, Rob Berendt <rob@xxxxxxxxx> 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
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.