On Tue, Jan 14, 2003 at 11:06:56PM +1300, James Collier wrote:
> [EMAIL PROTECTED] wrote:
> >Are there any docs for setting this up?
It isn't any different than setting up with seperate certs, just use the
same cert in each vhost.
> Not as such - I cooked the site up as a one-off, with the feelin
Are there any docs for setting this up?
thanks
Robert
- Original Message -
From: "James Collier" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 13, 2003 12:29 PM
Subject: Re: Confession: I use NBVHs with SSL (was Re: 2 VirtualHost
Mads Toftum <[EMAIL PROTECTED]> writes:
> On Mon, Jan 13, 2003 at 07:32:24AM -0800, Eric Rescorla wrote:
> > There is already a document describing how to do this with SSL/TLS
> > in the IETF standards pipeline.
> >
> Unfortunately this is not implemented very many places - so far the only
> plac
On Mon, Jan 13, 2003 at 07:32:24AM -0800, Eric Rescorla wrote:
> There is already a document describing how to do this with SSL/TLS
> in the IETF standards pipeline.
>
Unfortunately this is not implemented very many places - so far the only
place I've heard of is Apache 2.1 which has some prelimin
"Boyle Owen" <[EMAIL PROTECTED]> writes:
> - IPv6 will take off, creating so many IP addresses that NBVH will be
> unnecessary and we will revert to one site, one IP.
There is already a document describing how to do this with SSL/TLS
in the IETF standards pipeline.
-Ekr
--
[Eric Rescorla
>-Original Message-
>From: James Collier [mailto:[EMAIL PROTECTED]]
>
>At the moment, the handshake take place using the first matching vhost
>on the basis of IP+Port, but evidently Apache then scans the decrypted
>host header and assigns the correct NBVH.
Exactly. The SSL transaction i
>-Original Message-
>From: James Collier [mailto:[EMAIL PROTECTED]]
>
>I realise I am on thin ice as it would be a "reasonable"
>optimisation to assign the final virtual host at an earlier
>stage than is currently the case with SSL.
I wouldn't worry too much. Currently, in an SSL transac
>Sent: Montag, 13. Januar 2003 04:23
>To: [EMAIL PROTECTED]
>Subject: RE: Confession: I use NBVHs with SSL (was Re: 2 VirtualHosts
>with 2 Certificates)
>
>
>>These NBVHs are all derived off the same 3rd-level domain,
>and thus we
>>can use the same wildcard
On Sun, Jan 12, 2003 at 09:23:27PM -0600, Barry Smoke wrote:
> o.k...you have my attention now...
> wildcard certificate?
> Can wildcard certificates be purchased, or is this only if you are self
> signing?
>
According to Thawte's website they still issue wildcard certs.
> I sure would like to bu
>These NBVHs are all derived off the same 3rd-level domain, and thus we
>can use the same wildcard certificate for each NBVH (users whose
>browsers don't recognise wildcard certificates need only placate the
>browser once in most cases).
o.k...you have my attention now...
wildcard certificate?
ge-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of James Barwick
Sent: Wednesday, January 08, 2003 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: 2 VirtualHosts with 2 Certificates
Should have read the MOST FREQUENTLY ASKED FREQUENTLY ASKED QUESTIONS!!!
Can't do that. Learn a li
>-Original Message-
>From: Irving Carrion [mailto:[EMAIL PROTECTED]]
>Sent: Donnerstag, 9. Januar 2003 15:42
>To: [EMAIL PROTECTED]
>Subject: RE: 2 VirtualHosts with 2 Certificates
>
>
>Everyone knows this question will not stop coming... is it possible to
>ret
4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: 2 VirtualHosts with 2 Certificates
Should have read the MOST FREQUENTLY ASKED FREQUENTLY ASKED QUESTIONS!!!
Can't do that. Learn a little more about SSL. It's IP based, not name
based. So, you can only have
one certificate and one firtu
Should have read the MOST FREQUENTLY ASKED FREQUENTLY ASKED QUESTIONS!!!
Can't do that. Learn a little more about SSL. It's IP based, not name
based. So, you can only have
one certificate and one firtual host on 92.35.28.17:443. Sorry...but
that's the way it goes.
Same question answer numbe
Per all the documentation and countless examples in the archives of
this mail list, you must either use two different IPs or use different
ports. You *cannot* used Named Virtual Hosts for SSL. Period.
-dsp
On Wednesday, Jan 8, 2003, at 13:58 US/Eastern, toxshark wrote:
ihave the apache confi
On Wed, Jan 08, 2003 at 07:58:10PM +0100, toxshark wrote:
> i have the apache configured with 2 VirtualHosts on port 443.
> both VirtualServers have separately CertificateFiles and
> CertificateKeyFiles.
> but now if i connect to the VirtualHost2, the Host have the Certificate
> from the VirtualSer
16 matches
Mail list logo
