Re: [cobalt-users] secure certificate not active?

[shimi <shimi@xxxxxxxxxxxxxxxx>]

On Tue, 3 Jul 2001, Garry Mills wrote:

> Hi - 
> 
> I followed the procedure for obtaining a Thawte certificate by:
> 
> Creating a self styled cert
> Sending the request to them
> They sent me the confirmation back, entered that in the appropriate 
> box and clicked Use Manually Entered Certificate
> 
> The GUI is now showing the details of the Thawte certifciate, which 
> I presume means that everything is OK
> 
> However, when I go into the GUI the certificate information states 
> it's a self generated one, and I can't https://www.... into any of the 
> other domains on the site.
> 
> Any clues gratefully received
> 
> Best wishes
> 
> Garry
> 

First, FYI, if you have a cert for a site on an IP, you can't have
differencet certs for other sites on the same IP. (That's a GUI
limitation, search this mailing list archives for workarounds)

So the real question is... When you double click on the lock icon in your
browser, does the Thawte cert details appears up, or are you listed as the
signer?

If the latter is correct, the webserver didn't get the cert right (it
happend to many people here) - I don't remember what
without-taking-box-of-the-net solution was given, you can search for that
in the archives, but rebooting the cobalt helped everybody...

If it's not the latter, please tell us some other thing... does the other
sites, which https:// doesn't work for them, are on the same IP like the
site you installed the cert on, or on some other IP?

If it's on the same IP, I don't have an answer to your question.
If it's not, I *think* that once a cert was installed on on IP, all other
IPs will stop listenin for SSL connects, until you install a self signed
cert on each one of them. I could be wrong though... I remember all what I
said in this paragraph only vaugely. 

- shimi.