Current prerelease is 1.2.5

1.2.4 is the first to introduce experimental Wayland support. Especially on KDE Plasma there are supposed to be some issues.

Lets test!

Why?

Regular RDP/VNC programs are hard to use in real scenarios, as they rely on IP addresses. RustDesk is easier as it uses a Rendezvouz server that can also be selfhostet or reimplemented.

  • aksdb@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    5 months ago

    They also document scripts to bootstrap clients on other OSses. And I don’t think you need Pro to build rustdesk yourself - they even document the process.

    • boredsquirrel@slrpnk.netOP
      link
      fedilink
      arrow-up
      12
      ·
      5 months ago

      To be fair, the APGL requires to publish code that is compilable. So giving instructions is pretty relevant for more complex projects.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        5 months ago

        They don’t define what ‘compilable’ means though (among many other things), and it’s pretty easy to come up with several different definitions of it that not everyone will agree with.

    • refalo@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      The one big thing they do hide behind Pro though, is authentication for the server side. With the free version, if your server is open to the internet, then anyone who knows the IP can use it to relay their clients as well.

      • aksdb@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        They still need to know the key. If you publicly distribute your config, that’s a problem. But IMO one even the pro version couldn’t solve.

    • TCB13@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      5 months ago

      The point is that under Windows you can change the App name to set credentials and other settings like this:

      rustdesk-host=mydomain.tld,key=eiu5pzFYlr5nY9i9yJp9smzzLnvx4XNX7O3SaNhkWS8=.exe
      

      But under macOS you can’t do it… just because they don’t want to.

      • aksdb@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        5 months ago

        The apps are bundled completely differently on OSX and Linux. It’s technically not possible to do the same thing there. Also this is not a free/paid limitation at all.

        They could maybe build a packaging tool that can customize the binaries (adding data to the PE executable in Windows and maybe a property file in OSX and Linux); but that’s quite some effort for not much gain.

          • aksdb@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            5 months ago

            I said it’s possible, just much more effort than the current solution which only requires reading and and parsing the process name on startup.

        • TCB13@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Under macOS it’s trivial to change the name of the application package without messing with other aspects of the packaging.

          • aksdb@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            5 months ago

            If it’s so easy to implement, go ahead and open a PR. The community will be thankful.