As well, as using a custom port, I've been thinking of allowing my Linode to accept incoming SSH connections on port 443, so I can connect from behind our corporate firewall at work. All connections are via key-pairing and password login is disallowed.

Are there any security implications to this? I know we're discouraged from using 'common' ports for SSH, but it seems to me the most straightforward way to get past the work firewall and disallowing password login should make things pretty secure. Besides which, the Linode Lish console listens on port 443, so it can't be *that* bad, can it?

_________________
**************************
Mental Diarrhoea
**************************

Which port you use has 0 effect on the security of your SSH service. If someone discourages you from using "common" ports for SSH, that's a sign that you shouldn't be taking security advice from them.

- Les

I'm using sslh on other vpses of mine, which effectively allows me to run both ssh and https on the same port. whether this is suitable for you or not really depends on your situation. An added benefit is that the newest versions coupled with a recent linux kernel can do transparent proxying

Well, I let Google's mailservers take care of email for me. So I don't have anything else using 443 on my Linode. Sounds like I'm good to go for using that as an additional SSH port then.

Ta!

_________________
**************************
Mental Diarrhoea
**************************

There's no real security implication on your linode in running sshd on port 443.

There might be security implications for your job if you're using this to bypass corporate control policies! At my place this could lead to disciplinary action up to and including termination.

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)

Wha -- why would you be using Port 443 on e-mails? 443 is HTTPS.

I mean, you could use 443 - but you won't be able to use SSL on your website

- Dave