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.

  • foremanguy
    link
    fedilink
    76 days ago

    Just the old .ssh/config file, works like a charm on all terminals :)

    • @plumbercraic@lemmy.sdf.orgOP
      link
      fedilink
      13 days ago

      that is cool. I hadn’t tried konsole before - there are menus for days in here, I’ll never get any work done lol. Slick, and makes that fedora kde fling I have been considering more tempting.

      • @ikidd@lemmy.world
        link
        fedilink
        English
        12 days ago

        Fedora KDE is what I’ve settled on for the last couple years. I’ve used Linux a very long time, this setup has been completely painless since I installed, and always very up to date.

  • @Zeoic@lemmy.world
    link
    fedilink
    English
    15 days ago

    Odd that you have so many issues with Remote Desktop Manager, I use it all the time from my linux desktop, and both rdp and ssh work flawlessly

  • @CocaineShrimp@lemm.ee
    link
    fedilink
    English
    427 days ago

    Not a GUI, but I keep my ~/.ssh/config clean by splitting my configs into folders, and including them in the main ~/.ssh/config.

    I have the folder, ~/.ssh/config.d/, and here’s what it looks like:

    ~/.ssh/config.d
    .
    ├── work
    │   ├── dev.config
    │   ├── staging.config
    │   └── prod.config
    └── server
        ├── development.config
        ├── containers.config
        ├── home.config
        ├── pis.config
        └── server.config
    

    Then my ~/.ssh/config looks like this:

    Include config.d/work/*
    Include config.d/server/*
    Include config.d/other/*
    
    • Ashley
      link
      fedilink
      English
      56 days ago

      (looks at my 230 line config)

      yeah… maybe

    • Eager Eagle
      link
      fedilink
      English
      9
      edit-2
      7 days ago

      Cool, I did it with my git config a couple weeks ago, I didn’t know you could do it with ssh too.

      for those interested:

      [include]
      path = ~/.config/git/shared.ini
      path = ~/.config/git/dev-machine.ini
      path = ~/.config/git/aliases.ini
      path = ~/.config/git/self.ini
      
  • @BrilliantantTurd4361@sh.itjust.works
    link
    fedilink
    English
    97 days ago

    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.

    • @plumbercraic@lemmy.sdf.orgOP
      link
      fedilink
      37 days ago

      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.

      • @utopiah@lemmy.ml
        link
        fedilink
        26 days ago

        Folders, ssh, key auth, sftp and scp are the main things I’m looking for.

        suggesting that anyone who wants a central console for their remote systems must be somehow incompetent

        IMHO that’s exactly what ~/.ssh/config using its Include directive as shown in https://lemmy.ml/post/29858248/18510482

               Include
                       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.

      • @ikidd@lemmy.world
        link
        fedilink
        English
        2
        edit-2
        6 days ago

        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.

  • hendrik
    link
    fedilink
    English
    7
    edit-2
    7 days ago

    Uh, I just type ssh or rsync into the terminal and that’s it. It’s a manageable amount of computers/servers I connect to, so I can remeber their names. Regular ssh stores all the keys or custom ports / IPs in its config. What’s the advantage of using some manager?

  • @suicidaleggroll@lemm.ee
    link
    fedilink
    English
    7
    edit-2
    7 days ago

    How about XPipe?

    https://xpipe.io/

    It can even auto-configure itself by parsing out your ~/.ssh/config so you can keep everything defined there for easy CLI access but also use the GUI when desired.

    • @flubba86@lemmy.world
      link
      fedilink
      2
      edit-2
      6 days ago

      +1 for XPipe. This is pretty much exactly what OP is asking for. It also does SSH tunneling, SSH reverse-tunneling, manages connections into containers, and many other things. I’m a big fan.

  • Parade du Grotesque
    link
    fedilink
    57 days ago

    I would say, like many others, Remmina.

    Putty also has a Linux version, so you can use that as well. Its session management is a bit clunky, but it works and it offers some fairly good functionalities.

    But ssh is first and foremost a command line tool. As others have said, invest some time to learn its commands and configuration files.

  • @Peffse@lemmy.world
    link
    fedilink
    47 days ago

    I’ll be watching this discussion, as I’m currently using Remmina. It meet the bare minimum of SSH & RDP, but it doesn’t have a clear method to organize connections and instead uses a big list. I also find the interface a tad counterintuitive, so maybe I’m just using it wrong.

    It also seems to have a bug where it launches twice whenever I start my computer. So I have to close one.

    • @plumbercraic@lemmy.sdf.orgOP
      link
      fedilink
      17 days ago

      Portx, tabby and guacamole are my contenders so far. Guac would be needed for the graphical stuff - it’s sort of like a jump server running in a docker container that you would vpn into I guess? Neat concept.

  • @Valon_Blue@sh.itjust.works
    link
    fedilink
    37 days ago

    Use Tabby. It is, by far, the closest to a Linux terminal experience. Likely because it’s cross platform. I say this as someone that absolutely despises Windows terminal experiences.

    • @plumbercraic@lemmy.sdf.orgOP
      link
      fedilink
      25 days ago

      update to say that tabby is nice for ssh including key auth, and with profiles and groups it gets most of the job done. There is an sftp “plugin” but all it does is summon sftp. Will see if I can get it to open filezilla and use the env vars in calling the command. Setting aside RDP for now as guac looks like a good fit there.

  • @RandomChain@lemm.ee
    link
    fedilink
    3
    edit-2
    7 days ago

    I really like Asbru and have been using it for a couple of years. I used Remmina for a little while but never liked its look and feel.

    Not too much active development has been going on lately, sadly, but the latest version still works very well.

    https://www.asbru-cm.net/