It's not VPN endpoints we block, it's some ASN's that we've seen excessive amounts of abusive traffic from. Primarily that's isps in China, but I also added Zenlayer a while ago (which is the hosting provider your vpn endpoint was on).
I've removed them from the ban list, you should be good now. They might get readded if we see a flood of abuse from them though.
I just happened to see your comment, anyone can feel free to dm me if they have issues.
Most don't create new keys per server machine but that's not the issue. I don't bother, I create a key per client machine on my side.
Server gets compromised once, admin logs in and fixes it, admin logs in next time and the backdoor compromises it again.
That's all this is. If you can get in once, it's a spot you can leave a backdoor that many admins will miss. That's it.
Admins don't generally copy that whole file around, they usually copy and paste the lines they want. Also I generally copy and paste it from my workstation, not another server.
If your hosting is a bad actor, you're screwed no matter what. Why bother with this when they have direct access to your disk and ram
You could turn off authorized key files, or lock them down. This isn't really a big security risk though, there's countless ways to backdoor a system once you have access to do this.
This just targets a remote account, not your local pc.
It's not VPN endpoints we block, it's some ASN's that we've seen excessive amounts of abusive traffic from. Primarily that's isps in China, but I also added Zenlayer a while ago (which is the hosting provider your vpn endpoint was on).
I've removed them from the ban list, you should be good now. They might get readded if we see a flood of abuse from them though.
I just happened to see your comment, anyone can feel free to dm me if they have issues.