On Thursday 25 March 2004 10.12, Haim Ashkenazi wrote:
[...] decided to buy certificate from
versign [...]
[ok, this goes offtopic.sorry.]
You sure about that? Verisign is the company who break DNS (yes, the world
wide DNS. Not just their servers. Well, it *was* their servers, but that's
Adrian 'Dagurashibanipal' von Bidder wrote:
On Thursday 25 March 2004 10.12, Haim Ashkenazi wrote:
[...] decided to buy certificate from
versign [...]
[ok, this goes offtopic.sorry.]
You sure about that? Verisign is the company who break DNS (yes, the world
wide DNS. Not just their
I've checked the wildcard in the server name and it seem to work on
win2k and above, so I guess I'll stick to that.
It may have changed, but when I looked into this several years ago,
win2k didn't support star certs.
seph
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
seph wrote:
I've checked the wildcard in the server name and it seem to work on
win2k and above, so I guess I'll stick to that.
It may have changed, but when I looked into this several years ago,
win2k didn't support star certs.
well, I checked with updated version (all the service packs
On Thursday 25 March 2004 10.12, Haim Ashkenazi wrote:
[...] decided to buy certificate from
versign [...]
[ok, this goes offtopic.sorry.]
You sure about that? Verisign is the company who break DNS (yes, the world
wide DNS. Not just their servers. Well, it *was* their servers, but that's
Adrian 'Dagurashibanipal' von Bidder wrote:
On Thursday 25 March 2004 10.12, Haim Ashkenazi wrote:
[...] decided to buy certificate from
versign [...]
[ok, this goes offtopic.sorry.]
You sure about that? Verisign is the company who break DNS (yes, the world
wide DNS. Not just their
I've checked the wildcard in the server name and it seem to work on
win2k and above, so I guess I'll stick to that.
It may have changed, but when I looked into this several years ago,
win2k didn't support star certs.
seph
seph wrote:
I've checked the wildcard in the server name and it seem to work on
win2k and above, so I guess I'll stick to that.
It may have changed, but when I looked into this several years ago,
win2k didn't support star certs.
well, I checked with updated version (all the service packs
Michael Stone wrote:
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's probably not particularly useful
At 18:14 on Wed, 24 Mar 2004, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com, or you can go so far as to use * for any host
name. Most modern browsers
Haim Ashkenazi wrote:
Michael Stone wrote:
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's probably not
Michael Stone wrote:
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's probably not particularly useful
At 18:14 on Wed, 24 Mar 2004, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com, or you can go so far as to use * for any host
name. Most modern browsers
Haim Ashkenazi wrote:
Michael Stone wrote:
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default one
(key). I've looked in the documentation and found that ssl doesn't
On Wed, Mar 24, 2004 at 12:55:11 +0200, Haim Ashkenazi wrote:
I've looked in the documentation and found that ssl doesn't support name
based virtual domains.
Yes, see How to use TLS in application protocols under
http://www.gnu.org/software/gnutls/documentation/gnutls/gnutls.html for
details.
On Wed, Mar 24, 2004 at 12:55:11PM +0200, Haim Ashkenazi wrote:
(key). I've looked in the documentation and found that ssl doesn't support
name based virtual domains.
Correct; that would be impossible (the SSL session is established before
the client sends the name of the host it is looking for).
On Wed, Mar 24, 2004 at 06:22:35AM -0500, Michael Stone wrote:
On Wed, Mar 24, 2004 at 12:55:11PM +0200, Haim Ashkenazi wrote:
(key). I've looked in the documentation and found that ssl doesn't support
name based virtual domains.
Correct; that would be impossible (the SSL session is
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default one
(key). I've looked in the documentation and found
On Wed, Mar 24, 2004 at 12:18:58PM +0100, J.H.M. Dassen (Ray) wrote:
Yes, see How to use TLS in application protocols under
http://www.gnu.org/software/gnutls/documentation/gnutls/gnutls.html for
details.
Interesting - I didn't know this was possible! There's even support for it
in Apache
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
What if you had http://www.company1.com/ redirect to
On Thu, Mar 25, 2004 at 12:01:07AM +1100, Russell Coker wrote:
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
What if
On Wed, 2004-03-24 at 08:01, Russell Coker wrote:
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
What if you
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default
one (key). I've looked in the documentation and
On Wed, 24 Mar 2004, Haim Ashkenazi wrote:
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's probably not particularly useful for a virtual hosting
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default one
(key). I've looked in the documentation and found that ssl doesn't
On Wed, Mar 24, 2004 at 12:55:11 +0200, Haim Ashkenazi wrote:
I've looked in the documentation and found that ssl doesn't support name
based virtual domains.
Yes, see How to use TLS in application protocols under
http://www.gnu.org/software/gnutls/documentation/gnutls/gnutls.html for
details.
On Wed, Mar 24, 2004 at 12:55:11PM +0200, Haim Ashkenazi wrote:
(key). I've looked in the documentation and found that ssl doesn't support
name based virtual domains.
Correct; that would be impossible (the SSL session is established before
the client sends the name of the host it is looking
On Wed, Mar 24, 2004 at 06:22:35AM -0500, Michael Stone wrote:
On Wed, Mar 24, 2004 at 12:55:11PM +0200, Haim Ashkenazi wrote:
(key). I've looked in the documentation and found that ssl doesn't support
name based virtual domains.
Correct; that would be impossible (the SSL session is
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default one
(key). I've looked in the documentation and found
On Wed, Mar 24, 2004 at 12:18:58PM +0100, J.H.M. Dassen (Ray) wrote:
Yes, see How to use TLS in application protocols under
http://www.gnu.org/software/gnutls/documentation/gnutls/gnutls.html for
details.
Interesting - I didn't know this was possible! There's even support for it
in Apache
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
What if you had http://www.company1.com/ redirect to
On Thu, Mar 25, 2004 at 12:01:07AM +1100, Russell Coker wrote:
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
On Wed, 2004-03-24 at 08:01, Russell Coker wrote:
On Wed, 24 Mar 2004 22:22, Michael Stone [EMAIL PROTECTED] wrote:
The best you could do would be to attach different certificates to
different ports, but that would be extremely cumbersome and probably
would lead to confusion.
What if you
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default
one (key). I've looked in the documentation and
On Wed, 24 Mar 2004, Haim Ashkenazi wrote:
Haim Ashkenazi wrote:
Hi
I'm running a web (ssl) server with several virtual domains. at the moment
they are name based (non-ip) which of course produce a warning in the
user's browser when he try to connect to a host that is not the default
On Wed, Mar 24, 2004 at 06:14:52PM +0100, Elmar S. Heeb wrote:
Well, actually there is a solution: use wild cards in the name of the
keys. You can make the certificate for *.mycompany.com for several web
sites within mycompany.com,
That's probably not particularly useful for a virtual
38 matches
Mail list logo
