[–] 1 point 1 week ago* (last edited 5 days ago) (3 children)

You can’t load modules built with a different compiler.

Sure you can. There's even multiple guides for how to write C++ kernel modules, which inherently is going to use a different compiler than what was used for the kernel itself. BOSS Linux even writes C++ kernel modules.

if you want to use a module wrote in rust you also need to have built in the rust support in the kernel

Only if the module uses rust-specific interfaces in the kernel, otherwise it can be assembled into a .ko to have plain C-style symbols loaded by the kernel like normal.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago (5 children)

    you need to build the kernel with clang to build the kernel with the rust support

    I believe this statement is incompatible with how C works. The kernel can load modules written in any language as long as it outputs a .ko, so there can be no technical requirement for building the rest of the kernel itself with clang.

  • source
  • parent
  • context
  •  

    The free community version of Rustdesk Server (a competitor to the Teamviewer remote access software) is AGPL licensed.

    https://github.com/rustdesk/rustdesk-server

    The paid, proprietary Pro version builds on top of the community edition by adding extra features such as user authentication and a web backend for administration.

    There exists a repo for the pro server: https://github.com/rustdesk/rustdesk-server-pro

    But it only contains install scripts and no actual source code of the application.

    The github releases page of this repo however, contains the compiled code of the proprietary pro version and is available for anyone to download for free.

    Analyzing the disassembly of the pro and open source binaries shows that the pro version is definitely based on the open source version.

    The company previously associated with Rustdesk, Purslane Limited of the UK, is no longer in operation since 2023.

    The project has no CLA and so the dozens of previous contributors still hold the copyright to their code and have not given permission for it to be used in a proprietary version.

    There have been multiple requests for the source code of this pro version, but either there was no response or the issue was closed without comment.

    EDIT: The repo owner has completely deleted the issue, here is a screenshot: https://0x0.st/KaqD.png

    To me this just proves they know what they're doing is wrong.

    view more: next ›