What about the certificate installation on windows? Besides, I never claimed it’s malware, but it’s certainly software I wouldn’t trust.
When running older Rustdesk versions on wayland it would display a notification saying “Rustdesk doesn’t support Wayland yet”, containing a button labeled “Fix it”, which is the button you’re referring to. There’s no way for the user to know that clicking this button will edit their GDM config and disable Wayland.
This thread has a lot of reasons against rustdesk and also discusses some alternatives: https://discuss.tchncs.de/post/21632052
This. I also use udiskie on sway, works perfectly.
Yep, I’m not a Rust expert either, but this is pretty cursed. The comments on this post have some more examples of bad rustdesk code: https://lobste.rs/s/njfvjb/rustdesk_with_tailscale_on_arch_linux
Rustdesk looks good on the outside, but if you look inside, it has a really bad codebase and has done some sketchy stuff in the past.
Last year, it installed custom root certificates as trusted on windows, which is a huge security risk: https://github.com/rustdesk/rustdesk/discussions/6444
On linux systems, it forced its own autostart with no option to disable this behavior: https://github.com/rustdesk/rustdesk/issues/4863
In the past, when it didn’t have Wayland support yet, it edited your GDM config and just disabled wayland: https://github.com/rustdesk/rustdesk/blob/1.1.9/src/platform/linux.rs#L411-L422
Furthermore, the code quality is really bad. 90% of the linux platform-dependant code is just executing shell commands and parsing their output, while the same could be achieved in a safe way with proper rust builtins: https://github.com/rustdesk/rustdesk/blob/master/src/platform/linux.rs
While I agree that Rustdesk works pretty flawlessly, the codebase and the behavior of the developers made me distrust the software and I don’t recommend using it.
Try running ssh with -vv to get a better idea of the problem when no ssh agent is running.
Why would you want to do that? pacman attempts to connect via IPv6 first anyway.
I also host my own mailserver and I agree that it mostly works fine. However, there are some email providers that cause trouble:
Google seems to randomly sort some of my mails into the recipients spam folder, while others are delivered fine to the respective inbox. It kinda sucks that you can never be sure whether the recipient actually received your mail or whether they just don’t reply. My IP and domain are not blacklisted on any spam list; SPF, DKIM and DMARC are set up correctly as well.
Even worse is the Telekom (German ISP), who use an explicit whitelist of IP addresses (only IPv4 of course) and require you to display your contact information publicly on a website reachable via the same domain your mailserver uses. Once you’ve set this up you need to message them to be put on their whitelist. If you’re not on their whitelist, they simply reject your mails, they are not even delivered to the spam folder (maybe it’s not worse than Google, because you at least get a notice from your mailserver that your mail couldn’t be delivered). In the end I decided that I don’t care enough to comply with their regulations and just don’t send any mails to Telekom customers.
Aside Google and Telekom, I’ve really never had any issues though.
We’re not in disagreement about whether rustdesk is malware or not, but I think the developers being incompetent is also a perfectly valid reason to avoid it. Sure, they have fixed most if not all major issues that were reported to them eventually, but who knows when they’ll mess something up again.
Also, some issues weren’t really resolved timely, take for example the issue where rustdesk autostarted on each boot. That one has been actively ignored for over a year, which is the opposite of building trust.