You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
I noticed that the Docker Hub image rustdesk/rustdesk-server referenced by the official documentation) is build using a fork of this repository in the rustdesk-org GitHub organization: github.com/rustdesk-org/rustdesk-server.
Further, I found that each git tag in that fork has a commit, that is not part of the main repository and patches the source code using a hidden secret during the build process (see build.yaml). This looks like an attack where malicious code is added to the final binary, although the commit is created and signed by the same bot user as many other ones, also in the main repository.
Could anyone explain the reason for that fork and why the file src/common.rs is replaced during build?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I noticed that the Docker Hub image
rustdesk/rustdesk-serverreferenced by the official documentation) is build using a fork of this repository in the rustdesk-org GitHub organization: github.com/rustdesk-org/rustdesk-server.Further, I found that each git tag in that fork has a commit, that is not part of the main repository and patches the source code using a hidden secret during the build process (see build.yaml). This looks like an attack where malicious code is added to the final binary, although the commit is created and signed by the same bot user as many other ones, also in the main repository.
Could anyone explain the reason for that fork and why the file
src/common.rsis replaced during build?Thanks and regards,
lu1as
All reactions