Tag Info

Hot answers tagged

3

Drop bear might work. It does use the SSH protocol, but it doesn't share a code base with OpenSSH, so it probably won't crash in the same circumstances. I'm pretty sure you can configure both OpenSSH and Drop Bear to listen on ports other than TCP 22.


2

What is possible depends on what the firewall allows. If the firewall allows arbitrary traffic on port 443 Some firewalls take the simple way out and allow anything on port 443. If that's the case, the easiest way to reach your home server is to make it listen to SSH connections on port 443. If your machine is directly connected to the Internet, simply add ...


1

You could configure your SSH server to listen to both ports, and then use iptables to restrict access to port 22 to a single IP number. Something like the following (where x.x.x.x is the IP number you want to allow): iptables -A INPUT -p tcp --dport 22 -s x.x.x.x -j ACCEPT iptables -A INPUT -p tcp --dport 22 -j DROP


1

The MaxSessions parameter limits the number of multiplexed sessions you have on a single ssh session. Session multiplexing allows to setup a single Master connection which all other connections to the same host can then reuse. This has no effect on the ability to connect again to the same host via a new network connection. SSH has no way to limit or ...


1

The obvious answer for "remote shell" used to be telnet (urgh!). It seems that these days there is an SSL-enabled version of telnet, readily available on debian as: telnetd-ssl (I have to admit though, that I don't know anything about it as I've always been happy with ssh; given the bad reputation of telnet (mainly based on it's non-encrypted nature) I ...



Only top voted, non community-wiki answers of a minimum length are eligible