× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



+1.
We had some 3rd party apps that needed an alt SSL config or possibly an upgrade to support wildcard certs.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, April 06, 2016 11:24 PM
To: Midrange Systems Technical Discussion
Subject: Re: Wildcard certificate

Rob,

If the CN is dekko.com, it should only be trusted when connecting to dekko.com, and not customers.dekko.com or anythingelse.dekko.com.

To have a single certificate that works for all of customers.dekko.com, suppliers.dekko.com, foo.dekko.com, bar.dekko.com, etc, you should have a wildcard certificate, i.e. *.dekko.com.

The disadvantage to a wildcard certificate like this is that not all applications support wildcard certificates. It sounds like your "scanning service" is one such application. I'm not sure what a scanning service does? Security audits?

But, anyway, if you really want to be compatible with every application, you need separate certificates for customers.dekko.com, suppliers.dekko.com, etc, etc, each one with CN=whatever_it_is.dekko.com.

If you feel that it's important to use a wildcard so you have only one certificate, then you will have to live with the fact that there will be occasional applications that are not compatible with it.

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

-SK


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


--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.