In the help, there is a nice discussion about using PuttyGen to create SSH keys for use with AREDN nodes.
https://www.arednmesh.org/content/how-use-puttygen-make-ssh-keys-and-use...
Unfortunately, that is based on ancient versions of PuttyGen. The screen captures are so outdated, that I can't manage to create a key pair that will work with AREDN nodes. The options recommended simply don't exist.
Any chance of getting that page updated with screen captures from a reasonably current version of PuttyGen?
Or at the very least can someone walk me through what the settings need to be?
https://www.arednmesh.org/content/how-use-puttygen-make-ssh-keys-and-use...
Unfortunately, that is based on ancient versions of PuttyGen. The screen captures are so outdated, that I can't manage to create a key pair that will work with AREDN nodes. The options recommended simply don't exist.
Any chance of getting that page updated with screen captures from a reasonably current version of PuttyGen?
Or at the very least can someone walk me through what the settings need to be?
I see the docs have been updated. Tried several times with PuttyGen version 0.76 (current version). PuttyGen creates the files fine, but every AREDN node I attempted to upload the .pub file results in:
Jim, there's a good chance that your key file contains unwanted line breaks or other characters. I'm going to update the instructions to include WU2S Randy's previous way to remove those unwanted characters. Windows always makes things more complicated than they need to be IMHO. On MacOS, Linux, or Raspberry Pi it's fairly simple and straightforward using ssh-keygen.
Just as a followup to that. After not getting Windows to create the file, I used one of my RasPi-4s to generate a key pair, and the AREDN nodes accepted the file fine, but I could not get Windows to accept the file. I'm trying to use the SSH key file with a Windows command file that calls a bunch of scp commands. No matter what I did, scp would not accept the permissions of the key file - saying that the permissions were too loose. I did not try using the key file with Putty.
This had worked perfectly in the past, but as a result of a computer upgrade, lost the private key file, so trying to create a new key file pair. Tearing my hair out.
... well, if you're like me... hair is at a premium, so don't pull too hard! The latest instructions are in the GitHub approval queue tonight, so hopefully the online instructions will be approved and updated shortly. Is it possible that your Windows scp program is looking for its keys in a different location than where you created them with puttygen.
Good thought, but no. As you can see, the command file specifies where to look for the ident file, and the file is in the correct location. And it worked until I inadvertently killed the .ppk file.