Live data from Hacker News

MTPuTTY – Multi-Tabbed PuTTY

ttyplus.com

61–63 of 63 posts

Re: MTPuTTY – Multi-Tabbed PuTTY

#61

I did use MTPutty and then Kitty, but needing a mobile/tablet instance as well and tired of keeping .ssh copied to different devices to keep all of the connections & keys, etc. Was a pain, plus MTPutty did crash a lot for me. Termius, I found to be the best SSH client that works on all devices & OSs, including my laptop on Ubuntu. It's not free but worth the small amount it costs to be able to share connection settin…

(On windows) A 70MB download for a terminal? I'm already suspicious. This better not be an electron app :)

A yearly subscription, too? ugh.

Edit: It is an electron app. Pretty, though.

Re: MTPuTTY – Multi-Tabbed PuTTY

#62

I did use MTPutty and then Kitty, but needing a mobile/tablet instance as well and tired of keeping .ssh copied to different devices to keep all of the connections & keys, etc. Was a pain, plus MTPutty did crash a lot for me. Termius, I found to be the best SSH client that works on all devices & OSs, including my laptop on Ubuntu. It's not free but worth the small amount it costs to be able to share connection settin…

(On windows) A 70MB download for a terminal? I'm already suspicious. This better not be an electron app :) A yearly subscription, too? ugh. Edit: It is an electron app. Pretty, though.

Yes, it's electron unfortunately. So you're basically downloading chrome with a SSH node module & some interface code. I'm not a huge fan of it either, and even run slack in browser to save on memory on desktops. But the main features I have been after we're checked with termius. One of them being the yearly subscription of $10, but if it helps keep the devs active on it, I'm okay with paying for software, especially if it makes my job easier. Which usually includes lots of time in numerous SSH sessions.

Re: MTPuTTY – Multi-Tabbed PuTTY

#63

Earlier quoted context omitted.

As @Ineentho mentioned in another comment, I don't use username/password for ssh. I don't allow username/password for any system which I have responsibility (not even my local VMs for consistency's sake). I use ssh certs. My certs are passphrase protected, I enter the passphrase once at the beginning of a shell session and allow ssh-agent to handle subsequent logins. If I'm on a laptop at a client site in a cube or s…

Thanks! I only use username/password with my local mac and linux development systems. All of my cloud stuff is managed.

You might want to think about it even in those cases; not so much for security, but just to open up your options.

It takes me never more than a minute or two to do the one time setup for certificates in an new OS install, whether Mac or Linux (at least for personal dev machines). And once done, I'm free to use any ssh tools which use certs, which should be pretty much all of them, rather than those that cache username/password... or compared to the username/password entry time. I definitely end up saving time by reducing redundant entry and by being able to use the best tool for the job sans any other gating factor.

Naturally, this is all preference and you're free to choose things differently than I would suggest... but did want to offer you some food for thought.

Post reply on HN