On Sun, Nov 22, 2009 at 1:22 PM, Florent Georges wrote:
> Peter Schober wrote:
>
> Thanks all for your responses!
>
>> Or put all vhosts in the certificate (as X.509v3 SubjectAltName
>> extensions) and serve up the same cert on every vhost.
>
> Yes, that's what I started to think after have seen
Peter Schober wrote:
Thanks all for your responses!
> Or put all vhosts in the certificate (as X.509v3 SubjectAltName
> extensions) and serve up the same cert on every vhost.
Yes, that's what I started to think after have seen the other responses.
> How you put these in the CSR is not part
* Brian Mearns [2009-11-21 18:02]:
> Only the latest Apache (2.2.14) and OpenSSL built with the
> tlsextensions options support this. It's case SNI (Server Name
> Identification), where the client can send the fully qualified domain
> name as part of the handshake process. Without this, the server
Only the latest Apache (2.2.14) and OpenSSL built with the
tlsextensions options support this.
What about apache with mod_gnutls? Look at this tooltip from 2007:
http://www.g-loaded.eu/2007/08/10/ssl-enabled-name-based-apache-virtual-hosts-with-mod_gnutls/
Also, not every client support SNI,
On Sat, Nov 21, 2009 at 11:54 AM, Florent Georges wrote:
> Hi,
>
> I have one server one which I run two virtual hosts, say site1
> and site2. They run very well for HTTP stuff for months. Site1
> has also HTTPS access configured. I am trying to add HTTPS
> support for site2 as well. So I cr
Hi,
I have one server one which I run two virtual hosts, say site1
and site2. They run very well for HTTP stuff for months. Site1
has also HTTPS access configured. I am trying to add HTTPS
support for site2 as well. So I created a new SSL certificate,
and added a new file in sites-availabl
