From: Paulo Matos <[EMAIL PROTECTED]>
pjsm> On Wed, 18 Oct 2000, Vadim Fedukovich wrote:
pjsm>
pjsm> > I mean, it was answered, on this thread, several days ago.
pjsm> > To repeat it: ip address is the only way for a webserver
pjsm> > to choose a certificate/key to use for SSL handshake.
pjsm> > Usual instrument in plain HTTP, "Host: " header, is available
pjsm> > only after handshake.
pjsm> I follow this discussion, but there's something I could not
pjsm> get. How does the client/server behaves with this scenario: different
pjsm> certificates to the same ip, diffrent names to the same ip. Aren't we
pjsm> breaking something here?
Well, you're speaking about something that is basically impossible
with current practices. As far as I understand, it's rather difficult
to have the server use more than one server certificate...
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
