3 ms·
hmmm... if port NNNN got through, maybe it went to something already listening on NNNN? but an iptables redirect could fix that. just idle speculation. I'm p
by m463 3y ago
hmmm... if port NNNN got through, maybe it went to something already listening on NNNN? but an iptables redirect could fix that.
just idle speculation.
I'm pretty sure "Port" worked with older ssh servers, maybe. openssh was only 4 years old 20 years ago.
EDIT: hmmm what about needing privileges or an selinux config change?
- hnlmorg 3y agoUnlikely. While selinux is more than 20 years old, it was merged into the mainline kernel a few years after its initial release and it would have taken a while longer for that kernel to trickle down to distros, and then sysadmins installing.
- jtriangle 3y agoEven when it was trickled down to the distros, it was unfortunately very much in vogue to disable it... Hell even in current year I occasionally come across guides that suggest disabling it... great way to get ctrl-w'd smh