![]() ![]() We do this with PuTTY’s included PUTTYGEN.EXE file in the directory of where you installed/unzipped PuTTY to. The next step is to generate the key pair that you’ll configure your shell to use. It is now time to generate your Public and Private key pair that you will need to setup on the remote Linux box. It’s usually during this Save process that I may inadvertently click on one of the existing Saved Sessions, in which your profile is now completed wiped out and you have to start all over. You have now created your first Session profile in PuTTY. I like to call my sessions the name of my VMs, e.g. ![]() Then under the Saved Sessions textbox, enter a name for this session. Enter your username in the Auto-login username text box.įinally, to save your Session profile, click back on the Session category on the left. Set a default Username to login with by clicking the category Connection then Data.Make sure Port 22 and SSH options are set (usually the default).For the Host Name, enter the DNS or IP address.Open PuTTY and you should be in the Session category on the left.Here’s the steps I take to create a Session profile. Nothing worse than going through all the steps to create a Session profile, and missing one step, having it all wiped out to start over. Unless you hit Load, Save and Delete in the right sequence, things won’t be loaded, saved or deleted.īecause of this, I recommend setting up your Session profile first before we get started with SSH keys. Specifically, it is a bit quirky around the Sessions, aka Profiles that allows you to save settings for quick connections in the future (just select it, click Open and that’s it). It’s GUI though is a little odd and takes some getting used to. ![]() Ok, enough with reasoning – let’s setup PuTTY now. You can still use a passphrase in your scripts, and even encrypt it so it isn’t in the clear text. Less secure, but also less of a headache to setup. The easiest way to do that is to not use a passphrase, then the user account that the script runs under will have the ssh keys added allowing them to remotely signin. I also use them for script automation across multiple Linux machines, in which the script needs to log into the remote machine to perform commands. There are other reasons to use SSH keys for logins. You not only need my password but, you also need my certificate. That is my take on why I use SSH keys to sign into Linux machines. What if there was a way to sign your specific machine, say your desktop, to only allow connections from it? Then, combine that machine signature with yet another password (called a passphrase) for an impromptu two-factor authentication to login? (Factor 1, the certificate key Factor 2, your passphrase) The obvious issue is, what happens when someone gets your username and password? Yep, they can now login. Why use SSH keys to login?Įveryone knows you log into Windows and Linux machines with a username and password. Like my previous post on how to Create a Bootable USB Drive with Windows, I felt it was time to write my own step-by-step guide for my future reference.įirst, let me explain why I do this. In software, tools How to: Key-Based SSH Logins With PuTTYĪll too often I keep Googling this procedure to sign into SSH terminals with certificate keys since I’ve been switching to Linux for development. Eric Duncan spawning a race of beings Jul 1 st, 2014 by Eric Duncan ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |