Phoenix Network Forums

[SERVICE] - Please let sshd also listen at port 443 (unless used otherwise e.g. for https).

Reason: often firewalls do not support connections to port 22. But typically a HTTPS capable HTTP proxies support the HTTP CONNECT method, if the destination port is 443 (that's for HTTPS usually). Appropriate client programs can use that to connect to the SSH daemon (e.g. PuTTY).

Regards
Thomas

You can also use ftp, directadmin etc.
There's no need to add extra ports.

Rommaster wrote:You can also use ftp, directadmin etc.
There's no need to add extra ports.

Connecting via ssh offers a real shell, e.g. bash or tcsh: a fully operational CLI (command line interface).
FTP and directadmin don't provide that, sorry.

Of course there's no urgent need to let sshd listen also on port 443. On the other side the subtitle of this bulletin board is

"Have an idea that will make Phoenix even better? Post it here!"

therefore I've posted it

And as far as there's no other service planned on port 443, it's very easy. Just the following lines had to be added into sshd_config:

Code: Select all

Port 22
Port 443

In addition I don't see any impact on resources or performance. If I'm wrong, please tell me.

BTW, here's what the SSH FAQ says about this topic:
http://www.onsight.com/faq/ssh/ssh-faq-5.html#ss5.2

Regards
Thomas

What insane firewall must be to block 22 port? Even my network admin is mad one but he opened for me that port becouse everyone now knows how much means port 22. So if you have your own firewall in home i think you can fix that problem or just try to contact your ISP about that and say that they are morons if they blocking 22 port. Your ISP admins using that port even :-)

We have HTTPS.

thebeast wrote:What insane firewall must be to block 22 port?

Many companies configure there firewall to block port 22 because they think their employees don't need anything of the INTERNET but http/https.

Thomas

Tim wrote:We have HTTPS.

On every machine? Then sshd cannot listen on port 443, of course. Maybe one day, when a new machine is be added, port 443 of that machine can be dedicated to sshd rather than to https?

Thomas

there is only one machine (isn't there?) infinity. My suggestion is, if you have a problem with port 22, try and resolve it at your end.

My uni started to block all ports (except http/https) which was really annoying - way too many people complained - so they changed it. Now you just log into the firewall and you can use whatever port you like, and they just log your activity.

thanjee wrote:there is only one machine (isn't there?) infinity.

But http://wiki.phoenix-hosting.org/index.php/SSH_versus_Telnet says:

Phoenix Network uses SSH on all of its servers, for obvious security reasons discussed here.

"on all of its servers" made me believe there's more than just infinity. Shall I correct the wiki wiki article there?

Regards
Thomas

Anonymous wrote:[Posted: Tue Apr 04, 2006 9:55 am] ...

Oops, what happened? That was me. Didn't want to post anonymously, sorry. Seems that automatic login failed. Didn't even know that anonymous postings are possible.

Thomas

Anonymous wrote:"on all of its servers" made me believe there's more than just infinity.

I'd have a look at the last modified date on that article. It is almost certain it was written when we had 3 shitty servers compared to one good one.

That wiki isn't maintained.