3 ms·
~/.ssh/config is perfectly fine for that.
by fellerts 2y ago
~/.ssh/config is perfectly fine for that.
- samstave 2y agoNope. I've used linux since the 1990s. Was friends with the founders of LinuxCare, met Torvalds. blah blah blah... Since semi-retire from ops... and basically using windows for a few years without need to manage a linux box, youd be FN surprised how quickly basic knowledge evaporate at my age when not in use. I had to fn lookup how to add my keys to a box again. (After a 3-month long panel-interview with Google's Net Eng Team back in the day - my final panel question was: "OK how do you do a global search and replace in VI?" I *blanked* -- and I stated... "UH.... I'cant recall - id just google it" They all laughed. --- @OP -- look at the remote SSH extension in VSCode/Positron etc... Its a really good little file/function/SSH manager. Though Ill take a look at this.
- jbstack 2y agoIf the issue is forgetting basic commands / configuration options then how does swapping one tool for another help? You'll just forget how to use the second tool instead.
- GTP 2y agoThe second tool could be more user friendly, thus easier to remember how to use it. Compare how this tool makes you generate a key vs the syntax of ssh-keygen.
- yodelshady 2y agoWorth a chuckle from me too. I could and do type that all day, muscle memory. Verbalize it? Not a chance. There's a % in there somewhere. There does seem to be a subset of questions that are really just "have you repeatedly used this tool in the last few months?". If you have, you'll probably be fast.