for most part SSL cert providers doesn't generate and provide access through
their primary root servers. Most of the ssl vendors i.e. Verisign has differetn
intermediary root servers, which sometimes they call it by classes i.e. class1,
class2, class3 etc. Depending upon your business activity
Often the original cert contains the instructions inside it to automagically
install the intermediate, assuming the target server supports that technology.
I think IIS has since version 5.
From: Paul Hutchings [mailto:paul.hutchi...@mira.co.uk]
Sent: Thursday, October 14, 2010 1:17 PM
To: NT
I always thought that was the idea of wildcard certs, as long as the domain
part is the same it doesn't matter what the actual host name is. It's still
trusted by the issuers CA.
T
typed slowly on HTC Desire
On 14 Oct 2010 18:17, Paul Hutchings paul.hutchi...@mira.co.uk wrote:
Have to admit
I've imported it into a few servers and appliances (firewall for
example) and it works just fine, my browser doesn't complain and shows
it's trusted.
Note, if it's web facing web page or something, just install the Int.
Cert. I used a Cert once without installing the Int, it worked fine
:23 AM
To: NT System Admin Issues
Subject: RE: SSL Intermediate Certs
I've imported it into a few servers and appliances (firewall for example) and
it works just fine, my browser doesn't complain and shows it's trusted.
Note, if it's web facing web page or something, just install the Int. Cert. I
