Re: SSH - Port Conflict??


amerar@xxxxxxx wrote:
Todd H. wrote:
"amerar@xxxxxxx" <amerar@xxxxxxx> writes:

Hi All,

I'm trying to change my SSH port from 22 to 443. I was able to do that
on my previous install of Red Hat 9.0, which ran OpenSSH_3.6.1p2.

Now I am running CentOS 4.4 and when I change the port to run on 443,
the sshd process will not start. There are no messages in the log
either. The same behavior takes place if I try and run it on Port 80,
but the service starts if I use some other random port, like 55.

So, there seems to be a port conflict. CentOS is using OpenSSH_3.9p1.
It worked with Red Hat, so I'm at a loss as to why I cannot do this.

Any help please?

What's netstat -an | grep 443 say?


--
Todd H.
http://www.toddh.net/

Hi Todd,

Thanks for replying. Here is the output:

tcp 0 0 :::443 :::* LISTEN

Does that help at all?

It certainly is a clue.

Standard interfaces do not permit processes to bind to a port that is
already in use. Port 443 is the standard port for HTTPS, and port 80 is
the standard port for HTTP. If you have a webserver already active on
your system, it has already bound itself to port 80 and likely also
port 443. Any new program (like sshd) cannot bind to those ports
because they are already in use.

If you absolutely /must/ use port 443, shut down your webserver, or at
least disable it's use of HTTPS.

HTH
--
Lew

.

Relevant Pages

  • RE: [Full-Disclosure] Possible First Crypto Virus Definitely Disc overed!
    ... https without realizing it. ... Possible First Crypto Virus Definitely ... but I am about to block that port on my firewall. ... the governing KPMG client engagement letter. ...
    (Full-Disclosure)
  • Re: ISA 2004 HTTPS Protocol Port Addition
    ... HTTP will run any port "as is" with no rule changes. ... HTTPS will run on any port if you hack the ISA with a script to tell it to ... SSL Tunneling; Informational RFC ... Tunneling SSL Through a WWW Proxy ...
    (microsoft.public.isa)
  • Re: IIS 6 conflict using port 443 for NON-SSL traffic
    ... HTTP over IP1:Port1 and HTTPS over IP2:Port1 will be allowed ... think it may be possible to use this enhanced HTTPS.SYS with IIS 6 on WS03? ... > It actually has nothing to do with port 443 -- it could be any port. ... same web server, with one IP set up to handle NON ssl traffic ...
    (microsoft.public.inetserver.iis.security)
  • Re: ISA 2004 HTTPS Protocol Port Addition
    ... You *don't* create a new protocol. ... HTTP will run any port "as is" with no rule changes. ... HTTPS will run on any port if you hack the ISA with a script to tell it to ... Tunneling SSL Through a WWW Proxy ...
    (microsoft.public.isa)
  • RE: SSl on port 443 ?
    ... it's definetely Websense. ... I had a similar situation with an https site. ... The specified Secure Sockets Layer port ... Most Web browsers use port 443 for SSL requests. ...
    (microsoft.public.isa)