Restrict Custom Client Connections to Self-Hosted Server Only

[MAKISHIMAofN]

Dear RustDesk Team,

Could you please consider adding Advanced Settings to disable the following features built into the custom client?

• The ability to connect to another server
• The ability to connect to a public server

We would like to restrict connections so that our users can connect only to our self-hosted server when using the custom client.
Our goal is to prevent employees from transferring files to their personal computers.

Thank you for your consideration.

[MikeT-KBU]

Question, what are you doing, so they can't connect to your Custom server from home und use Transfer?

[MAKISHIMAofN]

I may not understand the intent of the question, but it is physically impossible to connect to our custom server (i.e., our self-hosted server) from a personally owned PC at home.

This is because the self-hosted server is on our internal corporate network and is not exposed to the internet.
Also, personally owned PCs cannot connect to our corporate network via VPN or any other method.

I have summarized the details below, so please review them.

Components

• Company-owned PCs
  A custom client created for our self-hosted server is installed.
  These PCs are located within the company and can store the company’s information assets.
  Employees are not able to install software. (For example, rustdesk-1.4.6-x86_64.exe)
• Personally-owned PCs
  rustdesk-1.4.6-x86_64.exe is installed and connects to the public server.
  These PCs are located at employees’ homes, etc., and we do not want company information assets to be copied to them.
• Self-hosted server
  A server we built internally within our company.
  It is not exposed to the internet.
• Public server / Another servers
  Your company-managed server that can be connected to via @public, or a self-hosted server built by a third party.

Current situation

1. Possible: From company-owned PCs, using custom client to connect to self-hosted server.
2. Possible: From company-owned PCs, using custom client to connect to public server or another servers.
3. Not possible: From personally-owned PCs, using standard client to connect to self-hosted server. (even if we use the custom client)
4. Possible: From personally-owned PCs, connecting to public server or other servers.

What we want to achieve

2. Not possible: From company-owned PCs, using custom client to connect to public server or another servers.