So now folks know what the StrictModes setting is for. You left your private key exposed, that's not good practice and you will get clobbered for that if it's on default. Having to use a vault for your keys in a corporate environment is OK (in corporate I would definitely also use a passphrase for my key), in my trusted home environment I really don't care that much.
Explicitly setting the correct permissions of the private key is deliberate. I wanted readers to know of it, because ssh-keygen doesn't mention this in its output. I could have left it out, but to know of what StrictModes is actually looking for may be helpful for the not so knowledgeable.
Ensuring you are permitted to login with your key by activating the already default "PubkeyAuthentication yes' is just insurance, a bit like installing rsync and sshfs when they are probably already there. No harm done. Overdone, maybe.
Notice I didn't disable password authentication. Again, in corporate I would have done.
BTW. Who is this man named OP.
Explicitly setting the correct permissions of the private key is deliberate. I wanted readers to know of it, because ssh-keygen doesn't mention this in its output. I could have left it out, but to know of what StrictModes is actually looking for may be helpful for the not so knowledgeable.
Ensuring you are permitted to login with your key by activating the already default "PubkeyAuthentication yes' is just insurance, a bit like installing rsync and sshfs when they are probably already there. No harm done. Overdone, maybe.
Notice I didn't disable password authentication. Again, in corporate I would have done.
BTW. Who is this man named OP.
Statistics: Posted by HanDonotob — Tue Aug 26, 2025 2:40 pm