After several weeks of very intermittent exercise, and some backsliding on the dietary controls, I’m back in the groove, I think …
Good exercise days – two days running at almost precisely the same pace. Excellent!
* * *
I use OpenSSH for nearly all of my computing platform access, except for that OS from Redmond. Secure access to commandline environments meets about 90% (a made up number, gut check says “true”) of my requirements. It’d be more, but I access a lot of monitoring services via a browser. But close to 100% of actual work is done via commandline remotely over SSH.
Every time I set up a new server, I’ve been logging into the new box and setting up the first user account with the appropriate public key. First I’d copy the key up to the new system, then I’d log in on the new box and run commands like these:
[user@box] ~# mkdir .ssh && chmod 700 $_ && touch $_/authorized_keys && chmod 600 $_ [user@box] ~# cat id_dsa.pub >> $_
How was I to know that in the intervening years, some one of the smart contributors to the OpenSSH project added the ssh-copy-id program. All I need to do from the client system is type something like this:
[user@client] ~# ssh-copy-id -i .ssh/id_dsa.pub user@box
It prompts me for my password, and the work is done. All of the directory and file work, correct permissions included (replacing those chmod commands), all done in one swell foop. Very handy.