Re: securing multiple websites using wildcard certificate - one IIS 6.0 server


"nix" <jyoo@xxxxxxxxxx> wrote in message
news:1148323912.250579.112800@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I do have three WEBSITES because they have different file structures.
One is a cgi enabled time *** tracker using a SQL backend and another
is a asp and another is a Microsoft CRM frontend. Therefore I have
separate icons on the tree in IIS. Each of these WEBSITES have their
own unique host headers associated to it all under *.domain.com as I
mentioned.


Oh, well in that case you cant do what you want to do. Period. (Certs aside,
which I think will cause a problem...the same cert on separate machines is
do-able, but on the same machine I haven't heard of yet.)

SSL encrypts from the IP address to IP address of the client/server
connection, basically at the TCP/IP level. So it happens on a lower level
than host headers operate (which is done by examining the contents of
unencrypted packets), thus, the host header information is ENCRYPTED when
the server wants to examine it to get traffic on your single IP to the
proper one of your three webs.

The result, is IIS will send the user using SSL to the default web on the
IP, or just throw an error.

To use three virtual webs with SSL, you need three public IPs on the outside
of the router, and three non-public bound to your NIC on the server.
Period. No way around it.


.