Curious what folks are using to organise their remote connections? I liked WinSSHTerm and have tried replacing it with Remote Desktop Manager, but it seems a bit broken (fonts look terrible in a terminal, sftp doesn’t work, RDP sort of works, but it’s not great).
RDP is not a must. Folders, ssh, key auth, sftp and scp are the main things I’m looking for. Currently considering Remmina but though I would check if ppl have strong views on this topic before trying the next app.
I’m using cinnamon with mint 22.
The reason you are having trouble finding a replacement is because thats not really how the linux world approaches things.
Learn the terminal, scp, ssh (esp key auth if you havent), sshfs, tmux, vim or emacs and you will find you are incredibly effective at modern admin tasks. If you havent already, look into something like saltstack or ansible to make your life even easier.
I use those tools already and have been administering Linux/bsd/docker for years. What’s new for me is using it as a desktop. The existence of scp, ssh etc dont solve this problem and while I find it interesting to learn how other admins are essentially making their own central console out of these components, it is a bit much seeing commenters insist that this is the same thing, or suggesting that anyone who wants a central console for their remote systems must be somehow incompetent. Sysadmins can have different workflow and tooling preferences.
IMHO that’s exactly what
~/.ssh/configusing itsIncludedirective as shown in https://lemmy.ml/post/29858248/18510482Include Include the specified configuration file(s). Multiple pathnames may be specified and each pathname may contain glob(7) wildcards, tokens as described in the “TOKENS” section, environment variables as described in the “ENVIRONMENT VARIABLES” section and, for user configurations, shell-like ‘~’ references to user home directories. Wildcards will be expanded and processed in lexical order. Files without absolute paths are assumed to be in ~/.ssh if included in a user configuration file or /etc/ssh if included from the system configuration file. Include directive may appear inside a Match or Host block to perform conditional inclusion.from https://man7.org/linux/man-pages/man5/ssh_config.5.html
So what I think people are highlighting is not that your need is wrong, rather that you rather than going back to fundamentals (e.g. lower command-line or even configuration here level stuff) you are looking for more complex and specialize tools. That tends to be reasonable in the Windows world where people are often looking for GUI but in Linux, started from Unix and thus CLI, this is a process that will often lead to disappointment. I believe people who are saying things perceived negatively here are pointing out, maybe poorly, a cultural difference that will be problematic in the future, thus why they are insisting.
Indeed someone else pointed out https://lemmy.ml/post/29858248/18514122
I’ve been using Linux for almost 30 years, and I agree with you completely. There should be a plethora of tools to organize SSH hosts, but unfortunately none of them are great, or at least I’ve never particular gelled with any. I just remember the hostnames and what user I happen to use for each, and copy my keys around, because I jump around between a lot of computers.
I did use SSHwifty for a while because then I could just jump into a browser and go to a webpage with all of them. Dunno why I got away from that, it was handy.