Hi Michael,
1) Each domain must have its own certificate.
2) Each domain that does not use SSL must be specified as such. (Turn SSL
off for that domain)
3) Any domain that will provide both regular and SSL connections must have a
virtual host set up for each listening on the appropriate port.
4) I cannot confirm or deny the single IP address theory, as I have not
tried it. But I do have some trouble believing it since the ServerName
directive is what gets matched against the certificate and the certificate
has no knowledge of the IP it came from. I could be wrong, it wouldn't be
the first time. But you will probably have to be quite creative about your
Virtual hosting directives to get things working. I would suggest hacking at
it a little before giving up. Especially since @Home is not likely to give
you additional IP addresses just so you can go against their service policy.
5) For the proper set up and directives that you need to use you should go
to www.apache-ssl.org. I would help you out on the directives but I use
mod_ssl and they have different directives, so you are on your own there.
Have fun,
--
_________________________________________________________________
Brian Ashe CTO
[EMAIL PROTECTED] Dee-Web Software Services, LLC.
http://www.dee-web.com/
-----------------------------------------------------------------
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one.
Thursday, June 15, 2000, 8:27:53 AM, you wrote:
MJM> Good Morning:
MJM> I'm running Apache-SSL 1.3.12 on my machine at home. I'm interested in
MJM> setting up virtual domains so that at least 2 of the domains I host can
MJM> take advantage of the secure connection. Under regular Apache, I would go
MJM> in and set up the following:
[snip]
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
