> > 1) I just went to https://certs.tucows.com/ and my browser Netscape 4.7
> > said that it did not recognize the authority that signed the certificate.
> > Netscape 4.7 is still widely used.  I thought that the Certs were going to
> > be backwards compatible?
>
>This is probably a configuration issue on the server, the CA cert
>chain has to be loaded and configured on that host's configuration for
>it to avoid that error.   (I'm guessing here based on experience with
>Equifax's certs which work similarly)


So this is not an issue of the Cert, but rather the way Tucows set it up on 
their server?  Because I got a warning in IE5 too, but I noticed that both 
these are mentioned as supported in the browser chart.


> > 4) Can we now or we will be able to in the future get wild card Certs?  So
> > that I can use one Cert for any number of sub-domains?
>
>I looked on Entrust's own site, and don't see wildcard certs offered.
>I don't think Verisign offers them either (well they do through Thawte
>still, but I imagine that will go very soon since that was in place
>before the acquisition).


Hmm. I didn't realize that they weren't offered by Verisign either.  My 
host uses one and gives me a sub-domain on their secure sever.  Does that 
mean that they will lose that ability?  I was hoping to be able to do 
wildcard certs to be able to offer my hosting clients the same set up.

Another question about these certs.  They are 128-bit right?  But will they 
still work in a browser that only supports 40-bit strength?

Also, the agreement that I agreed to online for selling certs, is that 
available in a printable format somewhere?



Jennifer

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Looking for books, software, movies, music...
http://www.chapters.ca/Default.asp?AFFID=108464
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Quality Children's Products - http://Store.MomsAtHome.ca/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your own domain name for as little as $13 US
http://www.mahDesigns.com/domains/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to