.
- Original Message -
From: Kishore Jalleda
To: users@httpd.apache.org
Sent: Thursday, April 13, 2006 11:35 PM
Subject: Re: [EMAIL PROTECTED] Apache SSL port question
The first thing is there is no obvious advantage of using a different port
for SSL, usually people tend to run standard
The first thing is there is no obvious advantage of using a different port for SSL, usually people tend to run standard services on non-standard ports mainly to decieve/hide your Services (SSH, etc) from external network scans.
As an example some people tend to run their SSH on a different port
Gary,
In general, the client, normally a web browser, knows that https is done over port 443. So most browsers will go to port
443 automatically when the URL begins with https. There is really no way to 'trick' the browser from the server-side. I
assume that the idea of moving the HTTPS listener
On 4/13/06, Schultz, Gary - COMM <[EMAIL PROTECTED]> wrote:
>
> I'm testing SSL (mod_ssl) on Apache 2.0.55 Win32. Some consultants that
> conducted a security analysis suggested using ports other than the default
> 443 port for SSL. Is it possible to configure Apache to use a port other
> than 443
Suggest you get new consultants. ;)On 4/13/06, Schultz, Gary - COMM <[EMAIL PROTECTED]
> wrote:
I'm testing SSL
(mod_ssl) on Apache 2.0.55 Win32. Some consultants that conducted a
security analysis suggested using ports other than the default 443 port for SSL.
Is it possible to configure
I'm testing SSL
(mod_ssl) on Apache 2.0.55 Win32. Some consultants that conducted a
security analysis suggested using ports other than the default 443 port for SSL.
Is it possible to configure Apache to use a port other than 443 for SSL and have
the URL stay the same, that is, be able to use
