The problem is not that’s to easy for you to log in, the problem is that everyone else can try it too. If there are no additional mechanisms in place, such as fail2ban, an attacker will have endless time to try to guess your password or even worse the root password.

Step 1: Create a ssh key

First lets start with the key generation for your client

ssh-keygen -a 100 -t ed25519 -f ~/.ssh/example.com_id_ed25519

You have once again committed with your private mail address in a repo where you should actually use your company profile?
Does this sound familiar to you?
I know this only too well, sometimes noticed early enough but mostly my private profile ends up in the commit!

So if we can’t manage to remember to use the right config by ourselves, then this must happen automatically.