Ich werde ab 24.03.2004 nicht im Büro sein. Ich kehre zurück am
25.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
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
Hi there,
one of our servers (which runs Debian Woody) was recently
compromised, and had a suckit variant installed. We've gone through the
reinstall and restore steps, and one of the things I looked at is
debian's /usr/sbin/checksecurity script, which checks for changes in
setuid files.
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, Mar 24, 2004 at 10:55:08AM -0300, Christian Robottom Reis wrote:
Hi there,
one of our servers (which runs Debian Woody) was recently
compromised, and had a suckit variant installed. We've gone through the
reinstall and restore steps, and one of the things I looked at is
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
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : [EMAIL PROTECTED]
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Re: Delivery Server
Nombre del archivo adjunto: data.zip
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es absolutamente
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : [EMAIL PROTECTED]
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Re: Failure
Nombre del archivo adjunto: details.zip
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es absolutamente
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : [EMAIL PROTECTED]
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Hello
Nombre del archivo adjunto: software.doc.exe
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es absolutamente
imprescindible
Ich werde ab 24.03.2004 nicht im Büro sein. Ich kehre zurück am
25.03.2004.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
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.
Hi there,
one of our servers (which runs Debian Woody) was recently
compromised, and had a suckit variant installed. We've gone through the
reinstall and restore steps, and one of the things I looked at is
debian's /usr/sbin/checksecurity script, which checks for changes in
setuid files.
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, Mar 24, 2004 at 10:55:08AM -0300, Christian Robottom Reis wrote:
Hi there,
one of our servers (which runs Debian Woody) was recently
compromised, and had a suckit variant installed. We've gone through the
reinstall and restore steps, and one of the things I looked at is
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
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : debian-security@lists.debian.org
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Re: Delivery Server
Nombre del archivo adjunto: data.zip
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : debian-security@lists.debian.org
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Re: Failure
Nombre del archivo adjunto: details.zip
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es absolutamente
Nuestro sistema antivirus ha
rechazado el siguiente email:
De : debian-security@lists.debian.org
A : [EMAIL PROTECTED]
CC : [No Cc Addresses]
Tema: Hello
Nombre del archivo adjunto: software.doc.exe
Copia de este aviso ha sido enviada al remitente
del mensaje. Si el correo es absolutamente
36 matches
Mail list logo
