# Change to no to disable tunnelled clear text passwords $ cat ~/.ssh/$KEYNAME.pub > > ~/.ssh/authorized_keys rm ~/.ssh/$KEYNAME.pubįinally, disable password access (optional): $ scp ~/.ssh/ssh/$KEYNAME.pub you SSH your remote machine and set the public key you just sent in your authorized_keys. $ ssh-keygen -t rsa -f ~/.ssh/ssh/$KEYNAME -C send the public key to the remote machine: Note that introducing a password is optional: Not only does this free you from entering your password every single time, but it dramatically increases the security of your remote machine. This is done by generating a new pair of keys, setting a password for them (if you feel like it), sending then to the remote machine, and eventually disabling password access.įirst, generate the public and private keys. The first step is dropping passwords and using ssh keys. In this post, I will describe my setup which, after over a month of being in production, has proved to make my life easier. Although this can be mitigated by merely using zsh’s substring history search, aliases, etc., I found it easier to offload the responsibility to my muscle memory. One major issue I have encountered is that SSHing different servers entails (i) having a mental map of which terminals correspond to which machines, and (ii) the overhead of introducing a SSH line immediately after opening a new terminal window. Since I do all my job from the terminal, I end up using SSH extensively. I use my MacBook as my main machine from which I access daily a number of servers that I use for development, experimentation, and maintenance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |