

21·
2 months agoBad eh security advice: use an alternative ssh port. Lots of actors try port 22 and other common alternatives. Much fewer will do a full port scan looking for an ssh server then try brute forcing.
Aka csm10495 on kbin.social
Bad eh security advice: use an alternative ssh port. Lots of actors try port 22 and other common alternatives. Much fewer will do a full port scan looking for an ssh server then try brute forcing.
Another option if you need public access without something like tailscale would be to use ddns and a AAAA record. Something like https://github.com/ddclient/ddclient would help do that.
That way if the IP changes, you’d pick up on the change for your vanity url within a few minutes… and can get https certs for that url as well.
Edit: I reread the OP. This doesn’t help if clients need direct ipv4. Sorry about that.