I recall that back in the world of $work I could never get keys generated with PuTTyGen to connect via SSH/SFTP to the Linux/Unix servers I was supporting
Odd, I've been using puttygen-generated keys to connect from at least Win7 and now Win10 to a variety of linux systems since at least 2013 ... and probably even before that; that's just the date of the oldest key I still have a record for; I may have even started on XP (I'm not sure, but I held out on XP for a long time before going to Win7). My current key is RSA key, using 4096 bits.
Unlike Aldebaran, I don't hardlink to the key; I have used pageant (or a pageant-compatible key agent plugin in my password manager), and that works just fine. But I cannot imagine that putty has difficulty with files but not with a third-party pageant-clone.
Like hippo, I think this doesn't have so much to do with perl (yet)... though since the next step after getting the keypairs working will be to try to connect using perl, and we'll probably be asked to help with that after this is working, it's a good starting point to have confirmation that Aldebaran can connect using putty directly... and then support of the perl connection can continue in the same thread. :-)
| [reply] |
Like hippo, I think this doesn't have so much to do with perl (yet)... though since the next step after getting the keypairs working will be to try to connect using perl, and we'll probably be asked to help with that after this is working, it's a good starting point to have confirmation that Aldebaran can connect using putty directly... and then support of the perl connection can continue in the same thread. :-)
Let me first address the topicality. At this point, I'm addressing things that are implementation specific in a couple ways. First is that I am on the windows platform. It's truly one of the bummers of the windows platform that I have to fight to make this happen. Also, I wouldn't want bliako to think that I've lost faith in unix. The truth is that I would install a dual boot ubuntu, but I can't get the darn thing to restart cold and look at the thumb drive. So I have to live in windowsland on my nice new machine for the time being.
Additionally, this question is implementation specific in that it considers Strawberry Perl first. I took soonix's downthread advice and installed Git, and with the way perl is behaving, I'm genuinely confused. For those uninterested in this implementation-specific problem, I invite you to skip the content between the readmore tags (maybe the entire thread if you're tired of posts about getting strawberry perl configured):
Fishing for tips,
| [reply]
[d/l]
[select] |
As mentioned elsewhere, git for Windows includes its own Perl. This seems to interfere with your Strawberry Perl.AFAIR the git installation asks how to handle the PATH, my choice is usually the most cautious one, and I call Strawberry Perl usually via the portableshell.bat to avoid this situation.
Update: You probably checked "Use Git and optional Unix tools from the Command Prompt", my choice is usually "Git from the command line and 3rd-party software", or (seldom) "from Git Bash only".I don't know, however, whether it is sufficient to remove something from the system PATH, or you'd need to un- and reinstall git to change this setting.
| [reply]
[d/l] |
