Passwords will be brute forced if it can be done offline.

Set a good high entropy password, you can even tie it to your login password with ssh-agent usually

Private SSH keys should never leave a machine.

If this actually matters, put your SSH key on a yubikey or something

If a key gets compromised without you knowing, in worst case you will revoke the access it has once the machine’s lifespan is over.

People generally don’t sit on keys, this is worthless. Also knowing people I’ve worked with… no, they won’t think to revoke it unless forced to

and you will never revoke the access it has.

Just replace the key in authorized_keys and resync

And you may not want to give all systems the same access everywhere

One of the few reasons to do this, though this tends to not match “one key per machine” and more like “one key per process that needs it”

Like yeah, it’s decent standard advice… for corporate environments with many users. For a handful of single-user systems, it essentially doesn’t matter (do you have a different boot and login key for each computer lol, the SSH keys are not the weak point)

If the keys are password protected… eh why not sync them.

Also ssh certificates are a thing, they make doing that kind of stuff way easier instead of updating known hosts and authorized keys all the time

That’s surprising, considering CGNAT would break it as well and is meaningfully common.

Potentially stability improvements as well (for the same reasons as the security improvements), especially for lesser used drivers and stuff.

Probably, unless they have a static delegation or do prefix delegation properly, which if they did they probably don’t suck enough to require double NAT^ lol

^single NAT for IPv6, assuming they don’t NAT it themselves

You could always do double NAT (put your own router behind theirs) as last resort. It’s not that bad, I’ve done it a lot.