× 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.  Home
  2. MIDRANGE-L
  3. April 2016

Re: Wildcard 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.


Seems to be a fault of the scanning service if it can't recognize a
wildcard certificate.


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


Right, seems they should recognize wildcard certificates.


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


Your CA could issue a certificate for dekko.com. But it wouldn't be a
wildcard certificate. And you couldn't use it for sub-domains like
customers.dekko.com. And it wouldn't fix the problem with the scanning
service.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.