At this point I could go BACK to my Windows' Visual Studio Code launch.json and simplify it to NOT use Plink/Putty and just use ssh and the ssh key management that's included with Windows. The key fingerprint key's randomart image is:Īuthorized_keys id_rsa id_rsa.pub $ exitĬ:\Users\scott\Desktop> type C:\Users\scott\.ssh\id_rsa.pub | ssh 'cat > password:įab. Your public key has been saved in C:\Users\scott/.ssh/id_rsa.pub. Your identification has been saved in C:\Users\scott/.ssh/id_rsa. C:\Users\scott\Desktop> ssh-keygenĮnter file in which to save the key (C:\Users\scott/.ssh/id_rsa):Įnter passphrase (empty for no passphrase): Generating SSH keys in Windows 11 is easy and convenient using the steps above. Now when I ssh I should NOT be prompted for a password.The ~ folder is implied but could be added if you like. I'm type'ing (cat on Linux is type on Windows) that text file out and piping it into SSH where I login that remote machine with the user pi and I then cat (on the Linux side now) and append > that text to the.Yours could be in a file you named earlier, be conscious. I'm "scott" on Windows so my public key is in c:\users\scott\.ssh\id_rsa.pub. You can see authorized_keys is in there, you may or may no have this file or folder. I ssh'ed over to Linux and note I'm prompted for a password, as expected.Just get the essence right.īelow, note that when the command line is C:\ I'm on Windows and when it's $ I'm on the remote Linux machine/Raspberry Pi. You can gen the key on the Linux side and scp it over, you can use a custom key and give it a filename, you can use a password as you like. Tell the Linux machine (by transferring it over) about the public piece of my key and add it to a specific user's allowed_keys.I want to ssh FROM here TO the Linux machine. I want to be able to type "ssh from my Windows machine and automatically be logged in. Level set - What are we doing and what are we trying to accomplish? You can see where ssh is installed: C:\Users\scott>where ssh I'll be ssh'ing with my Windows SSH into a remote Linux machine. Let's say now that I want to be able to ssh (shoosh!) into a remote Linux machine using PGP keys rather than with a password. You'll get all the standard OpenSSH stuff that one would want. In the list of features, select OpenSSH Server and click on the Install button. On the next page, click the button Add a feature. On the right, click Manage optional features. You can then add the client (or server) with this one-time command: Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0 Enable the OpenSSH Server in Windows 10 Open the Settings app and go to Apps -> Apps
0 Comments
Leave a Reply. |