Date: Wed, 21 Dec 2005 13:55:17 -0500 (EST) From: "Gary D. Margiotta" <gary@tbe.net> To: Jett Tayer <jett@angdatingdaan.org> Cc: freebsd-isp@freebsd.org, Kirill Ponomarew <krion@voodoo.bawue.com>, bostondriver@comcast.net Subject: Re: ISP's supporting sshd on port 443? Message-ID: <20051221135439.R53299@kerplunk.tbe.net> In-Reply-To: <62080.202.175.229.210.1135190098.squirrel@mail.angdatingdaan.org> References: <122020051635.14761.43A832C8000DE4BB000039A922058863609D0A90079D0B02019B9C010D@comcast.net> <20051220163947.GU2396@voodoo.bawue.com> <20051220123052.O46528@kerplunk.tbe.net> <62080.202.175.229.210.1135190098.squirrel@mail.angdatingdaan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yep, sorry I left that specific out. -Gary On Thu, 22 Dec 2005, Jett Tayer wrote: > 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. >> > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051221135439.R53299>