provided you will be running ssl-enabled web services.
but if not, apache and sshd running on port 443 will
work without a hitch.
I run an instance of sshd on port 443 as well on most of my servers, due
to firewall restrictions at some of my clients' sites. Mostly all of my
servers are FreeBSD, 4.x and 5.x, usually -STABLE branch.
The only problem I have run into is if I'm running web services (apache in
my case), I have to bind to specific IP's and ports in the apache conf on
the machine, as if you let it try to bind to all addresses, Apache
conflicts with sshd. Other than that, I've been running it like that for
almost 2 years now.
Re: Feedback solicited - best way to harden a mail/web server? ... > use," I've never heard of someone needing bind at home. ... Only when firewall admins poke open port 119 :-), ... what's what and then rerun chkrootkit.... no business leaving Apache at its default port. ... (comp.os.linux.security)
Re: Services listening on all ports? ...IIS does bind to all addresses. ...Apache does the same thing by default but if you add the address into the ... the same Port. ... (microsoft.public.dotnet.languages.csharp)
Re: File permissions for a wiki-like site ... to a single web server went out with browsers that don't understand ... Actually you can, and often do, have multiple instances of Apachelistening on port 80.. ... (comp.lang.php)
Re: File permissions for a wiki-like site ... to a single web server went out with browsers that don't understand ... Actually you can, and often do, have multiple instances of Apachelistening on port 80.. ... (comp.lang.php)
Re: Error 49, socket problem? ... I doubt it's a DoS attack, however it could very well be. ...apache runs on port 80 and 81. ... I've ruled out that it's a problem with the MySQL server in this case, ... (freebsd-net)
