3 ms·
> innocent bystanders as CGNs are deployed SSH is not HTTPS, a resource meant for the everyday consumer. If you know that you're behind a CGN, as a developer,
by qwertox 2y ago
> innocent bystanders as CGNs are deployed
SSH is not HTTPS, a resource meant for the everyday consumer. If you know that you're behind a CGN, as a developer, an admin or a tool, you can solve this by using IPv6 or a VPN.
> Worst case, this will give bad actors the option to lock the original owner out of their own server
Which is kind of good? Should you access your own server if you are compromised and don't know it? Plus you get the benefit of noticing that you have a problem in your intranet.
I understand the POV that accessing it via CGN can lead to undesirable effects, but the benefit is worth it.
Then again, what benefit does it offer over fail2ban?