3 ms·
it's fine until you run into some stupidly written tool or abstraction layer that relies on ssh being port 22. yes, it sucks to make efforts to accommodate you
by serf 3y ago
it's fine until you run into some stupidly written tool or abstraction layer that relies on ssh being port 22.
yes, it sucks to make efforts to accommodate your worst software, but sometimes it's easier to throw the cycles away than to dick around with a custom iptables entry to fix someone elses poor software design choices.
- BiteCode_dev 3y agoYou use ssh to proxy x to 22 and connect stupid tool to that.
- WesolyKubeczek 3y ago> it's fine until you run into some stupidly written tool or abstraction layer that relies on ssh being port 22. Good part of being me is not having to deal with such tools. If I see something like this, I consider finding an alternative immediately because the hardcoded port will be the least of its problems. If it assumes and insists on a port, there's a good chance it doesn't even piggyback on an ssh command or libssh and reimplements lots of ssh itself. What ever could go wrong with this approach? If it's a tool to which source is available, it can be patched up. It can be used on the right side of the LAN where you can use well-known ports all you want. Embrace and use VPNs, they are good! I'm somehow convinced that if the ground rules are laid out up front in no ambiguous terms, the workaround will be found on the side of the badly-written software.
- pepa65 3y agoNothing should rely on ssh being on 22 without taking config into account. Never use stupid tools!