Re: [cobalt-users] SSL Questions

["Robert G. Fisher" <rfisher@xxxxxxxxxxxxxxx>]

> 2)  Will I have any problems using continuing to use PHP in conjuction with 
> SSL?

Shouldn't, both php and ssl run as modules in Apache 1.3.x -- forget the
minor version number of apache shipped on the RaQ2.  You might want to
verify the httpsd.conf files though to see if it's loading the modules.

Hint:  You are not buying something completely new when you purchase
the Secure Server from Cobalt (or even RedHat) -- it's still Apache
and mod_ssl, what you are buying primarily however is first the
commercial license for SSL from RSA -- see the docs on mod_ssl, you
can download and compile it -- but can only use it with the general
license if it is not for commercial use.  The second thing you're buying
is the packaging -- where it comes in binary forms with all appropriate
binaries and an almost ready to go config file.

> 3)  With name based addressing, I understand that I can't run SSL on the 
> strictly name based sites, however, I assume that SSL *will* work on the 
> FIRST site that I use for name based hosting (because the first site will 
> have an IP address associated with it)?

Umm, actually SSL should work on the virtual host -- however you set it
up in httpsd.conf -- since the RaQ2's interface doesn't interact with
this file -- you just need to go edit here.  The default httpsd.conf
files that comes with the secure server are setup for a single site 
however.

> 4)  I currently own a versign certificate as my site has been on a 
> different server and I am currently migrating it to the Cobalt.  Does that 
> mean that I will have to get a new Thawte certificate or can I continue to 
> use the Verisign Cert? From reading the docs, I got the impression that the 
> RaQ2's did not work with Verisign.

I'm using a RaQ w/ a VeriSign cert and a RaQ2 with a Thawte cert.
Thawte certs are cheaper, for this year at least.  VeriSign certs
should work -- they use the same technology.  

I'm not sure about moving the certificate, I tend to doubt it -- but
in the case it would work -- you need to use gather both the key
and certificate file to move to the new site where you edit your
httpsd.conf to point to the appropriate files inside the VirtualHost
stanzas of the config file.

-- 
Robert G. Fisher		     NEOCOM Microspecialists Inc. 
System Administrator/Programmer      (540) 666-9533 x 116