3 ms·
The Rust Desk security concern is due to it's not 100% self-hosted, it uses some kind of TURN or fw hole puncher which they host and didn't provide the sources
by metadat 4y ago
The Rust Desk security concern is due to it's not 100% self-hosted, it uses some kind of TURN or fw hole puncher which they host and didn't provide the sources for.
If I'm mistaken please tell me, would love to use it if it's "safe".
- gerdesj 4y agoI've got a self hosted host in my office. When you deploy a client, you can rename the Windows exe to include the DNS name and public key of your host and it will then use them - clever idea. So I don't think you need their TURN/STUN. I suspect those are simply provided as a service and nothing more sinister. They also provide three or so really low spec jump boxes to get people up and running if they can't self host - again, I call that altruism not sinister. I will get Wireshark out anyway to check about this stuff next week. You can do your own real due-dil stuff yourself by browsing around this: https://github.com/rustdesk/rustdesk https://github.com/rustdesk/rustdesk - read the issues, browse the source (read the comments!) get a feel for the software. I'm asserting that it is no worse than anything else. I can also assert that the binaries that I get on Arch Linux are probably from the official sources (I checked a few strings etc). I can't sign off the Windows binaries but I can assert that I do trust them from their GitHub repo. I can assert things until I'm blue in the face but I trust rustdesk more than most remote access facilities for now but I am still kicking the tyres.