In message <[EMAIL PROTECTED]> on Mon, 08 Nov 2004 12:49:58 -0500, Charles B
Cranston <[EMAIL PROTECTED]> said:
zben> I guess my comments were kind of conditioned on the certificate
zben> being for HTTPS, however, the underlying problem occurs in all
zben> SSL transfers: when multiple domain name
I guess my comments were kind of conditioned on the certificate
being for HTTPS, however, the underlying problem occurs in all
SSL transfers: when multiple domain names resolve to the same IP
address there is no way for a server to know which of the
certificates to present, and since the negotiatio
I think the complication is that he's going to have to use
the virtual hosts stuff so that the correct certificate can
be returned to each connection, and that this means he's
going to have to have two different IP addresses, since there
will be no way to determine WHICH certificate to send.
This i
In message <[EMAIL PROTECTED]> on Fri, 5 Nov 2004 18:57:04 -0800 (PST), David
Smead <[EMAIL PROTECTED]> said:
smead> I'm running Debian testing.
smead>
smead> I have a machine with two static IPs, presently on one NIC
smead> using a virtual interface. I'd like to make two self-signed
smead> cer
David Smead schrieb:
Greetings,
I'm running Debian testing.
I have a machine with two static IPs, presently on one NIC using a virtual
interface. I'd like to make two self-signed certs, one per IP. Is this
possible given that the machine only has one hostname?
If it matters, the two IPs differ by
