[otterley]

Uh, why not? Unless your SSH client is on the same network as theirs, there are going to be middleboxes somewhere in the path.

[gsich]

Because your ISP should (and most do not) alter traffic.

[otterley]

But you’re not considering the many business environments that do.

[gsich]

I don't because that would be impossible. Every business has different rules. But if you (as a business) want to to use this, you will find a way to make the changes to those "middleboxes". It's not your network, it's your business's network.

[otterley]

Large multi-national corporations, by way of their sheer size, tend to force their vendors to bend towards their needs, not to adapt to meet their vendors' unusual networking requirements.

[gsich]

Thankfully SSH on non-22 is not unusual.

[otterley]

Of all the SSH servers in the world, what percentage are listening on a port other than 22? To answer this question, you can visit https://data-status.shodan.io/ports.html and see for yourself.

By "unusual," I literally mean "not usual/not typical." Not "never happens."