Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of mearns.b@gmail.com designates
 209.85.218.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=n30/8xjBWe3ntIiqt7kZ9PLtAW8saPETVQhARyeIIj9p3Vjv7iKctLoIh5mwEInzSi
         eVLn+L1IolLXHaEt2JVtrhcH5YEmMNUr3cMf5K1Fl1LGfRb1lB8KchiOqdrbSXA7HKJN
         B27DJH216djNvzAvJm5g8teaCdO7qpQnqOu/Y=
MIME-Version: 1.0
In-Reply-To: <716155.32752.qm@web23006.mail.ird.yahoo.com>
References: <20091122130753.GD6857@wssp.cc.univie.ac.at>
 <716155.32752.qm@web23006.mail.ird.yahoo.com>
From: Brian Mearns <mearns.b@gmail.com>
Date: Sun, 22 Nov 2009 13:26:30 -0500
Message-ID: <4df3a1330911221026h14a761ael30159d0b16d2c68d@mail.gmail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [users@httpd] Name virtual hosts and HTTPS

On Sun, Nov 22, 2009 at 1:22 PM, Florent Georges <darkman_spam@yahoo.fr> wr=
ote:
> Peter Schober wrote:
>
> =A0Thanks 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.
>
> =A0Yes, that's what I started to think after have seen the other response=
s.
>
>> How you put these in the CSR is not part of this list and
>> depends on your CA (some require to put all hostnames in the CN,
>> i.e. multi-valued CNs, others require to stick these in the
>> v3 extension.)
>
> =A0Well, I must admit I am not familiar with this vocabulary: CSR, CA, CN=
?
>
> =A0Thanks again,
>
> --
> Florent Georges
[snip]

CSR - Certificate Signing Request, the thing you send to a certificate
authority to request a certificate from them.
CA - The certificate authority who signs your certificate.
CN - Common Name, the thing that identifies the entity to whom the
cert belongs. For web sites, this is the exact domain name of your
website, other wise the client will complain.

Thanks to all for the follow up to my response, I had no idea there
were so many ways to do this. I just spent a few hours a couple of day
ago upgrading to 2.2.14 so I could do exactly this.

-Brian

--=20
Feel free to contact me using PGP Encryption:
Key Id: 0x3AA70848
Available from: http://keys.gnupg.net

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org