You get a nice clean interface with your SSH connections. It fixes every inconvenience I had so far with PuTTY. Solution? Hello PuTTY… I mean Solar-PuTTY So not only I have to close the window with an inactive SSH session, but I have to open a new instance of PuTTY, find the correct SSH profile and launch a new session. There is no way to reconnect the client or do anything from that window.
If you use PuTTY *(forgive me if I missed the config, I looked but I cannot find it), rebooting your Raspberry Pi will cause the SSH to disconnect (that’s to be expected) and by default (this CAN be changed) the SSH window will stay open. So what bothers me the most? A tedious way of managing profiles (this interface needs to change why PuTTY is stuck in the Win95 era?) and ending sessions on reboot. The interface and behaviour are so outdated, that it has taken the toll on me.
It’s great really, there is a small problem. Until now, PuTTY had been this “decent client”. My custom port forwarding configuration is – impressive! Dealing with many SSH enabled devices needs a decent SSH client. These are accessible from the local network as well as from the WAN.
I got a fair share SSH enabled devices running on my network.
