You can - but involves a lot more fucking around… I’ve seen plenty of “colleagues” use putty - but - they just point it at a server, and enter their user name and password EVERY FUCKING time! That’s not only wasting time, it’s so lame it’s STUPID, work smarter, not harder you moron!
e.g. if I want to take my id_rsa.pub and use it in putty - I have to convert the format (it’s not nearly as simple as renaming it to id_rsa.pem!) then I have to run it through some kinda processing thing that putty has before i can use it - and - I think I need to set it up for EVERY single putty “connectiion” I might keep in putty (which the fucking thing stores in the Windows registry).
On NIX systems, all my saved settings go in ~/.ssh/config - or - with later (e.g. less than 5 years old) version of openssh - I can nest/include config files :
╰─➤ cat ~/.ssh/config
I can do this in MacOS, recent Linux distros, FreeBSD running on TrueNAS, MobaXterm (which is really just repackaged cygwin - which I could do myself - but I’m lazy so I bought MobaXterm) and WSL* … I can edit those config files with vi or nano or whatever - I can store them all on some shared or sync’d cloud storage (in if I’m lucky, my $HOME is on an NFS share) - so they’re everywhere, wherever, I need them…
Note : I don’t think ~/.ssh/config file on Solaris can do nesting / includes, but then Solaris is steaming pile of crap (I used to swear by it - it was my bread and butter for many years - but I DETEST it when I come across it these days!).
Try that simplicity with putty - this is why I hate putty…
* it even works, from e.g. Windows 10, MS-DOS (it’s not actually MS-DOS - it’s “cmd”) prompt, I can have a C:\Users\myprofile.ssh\config - and I can ssh from the Windows 10 CMD, or maybe even powershell… I’d rather do that, than use putty even!