SimeonOnSecurity

Agreed. Even the self hosted relay option provides almost no logs. We want to see verbose logs with connection information to include IPs, ID info, hostnames, user permissions, connection type,...

A valid privacy policy should be defined. For this to be a truly open source project, any information that is collected should be documented and the client and server side...

Yeah, more specifically, we'd like the ability to lock the client to receive connections only from one relay or from one account. That plus enforcing 2fa on the accounts themselves...

> I have been trying out RustDesk-Server and i find it very stable, fast and well created. > > However i am running my own RustDesk-Server and i feel like...

If this is the case, some idiot proofing would be nice. At least grey the option out until it's ready... We shouldn't have to ask..

The easiest and most straight forward is to just charge businesses for continued support and possibly for custom builds or licensing for repackaging. It's not like we have to redefine...

> @paspo without --net=host, our P2P direct link (via hole punch) can not work, because hbbs can only get virtual ip of docker rathter than real ip of the connection....

Would just like to add that I'm running into the same issues. Unless my pr for the docs is accepted, with the current build and the current docker commands Because...

> @simeononsecurity please consider testing the alternative [rustdesk-server-s6](https://registry.hub.docker.com/r/rustdesk/rustdesk-server-s6) docker image > > it is a single image, with both executables (hbbr and hbbs) running as services, controlled by [s6-overlay](https://github.com/just-containers/s6-overlay). Some...

From the looks of it, it seems that either the Nessus File Path Quotation or the Windows 10 Package path is breaking it. With such an easy turn around to...