[FEATURE] - Connect even if device are not on same server

[Apashh]

Hey,

It will be interesting to connect to a public Rustdesk ID not hosting it on our servers while remaining connected to our hosted server.

Thanks for reply !

[ghost]

+1 for this. Currently if a customer installs RD themselves we cannot connect to it as it doesn't have our server credentials.

[mycanaletto]

Hello,

Any news about this feature?

[rustdesk]

#2118 #1873

[rustdesk]

@sahilyeole Let's support <id>@<host>[:port]?key=<value> in the id input box.

<id>@public means connecting to public server, key not needed in this case.

In this case, my_id (shown on remote cm window) sent to server should be <my_id>@<my_host> if my_nost != peer_host

[rustdesk]

@sahilyeole add some tooltip there to tell users how to use

[mycanaletto]

This is a good idea.

This will enable an isolated customer to install Rustesk without having to be given the key to connect to it the first time.

This raises the problem of the key. If the customer can copy the key, he can use our server for other devices without our knowledge.

We'd need to find a way of making it impossible to copy the key, or of making this possible only if the Rustdesk user is logged in. Otherwise, the key could spread and my server become public...

[pedjas]

We will address this issue in next Pro version.

This explains everything. We were just teased. FInal goal was to make commercial product an sell it to us.

Well, RustDesk is fine product, but while OpenSource. As commercial product it is far behind competition.

[pedjas]

This is a good idea.

This will enable an isolated customer to install Rustesk without having to be given the key to connect to it the first time.

This raises the problem of the key. If the customer can copy the key, he can use our server for other devices without our knowledge.

We'd need to find a way of making it impossible to copy the key, or of making this possible only if the Rustdesk user is logged in. Otherwise, the key could spread and my server become public...

One who sets self hosted Rustdesk would use it either for small group of people which leads to having option for them to log in. Other possible use is to provide support for number of other users by accessing their desktop. For such kind of remote client solution could be to allow only to share the screen not to see other's screen.

So in final: if user is not logged in, he can only share his screen. If he logs in, then he can use server to access other's desktops. There could be option for logged in user to share his screen to remote user even if that one is not logged in.

[mycanaletto]

I bought a license that supports 500 devives. The group is not very small....

Perhaps it should be possible to define several keys and limit them to one group?

[rustdesk]

We'd need to find a way of making it impossible to copy the key, or of making this possible only if the Rustdesk user is logged in. Otherwise, the key could spread and my server become public...

This is pretty a good idea, we will think about this. Thanks @mycanaletto

[pdifeo]

I agree but only if the user can logout and the key is still configured on the client.

[pdifeo]

I agree but only if the user can logout and the key is still configured on the client.

Another solution is protect configuration with an additional passwork, like TeamViewer with "Option Password"

[rustdesk]

Below works on 1.2.4 (current nightly build). https://github.com/rustdesk/rustdesk/releases/tag/nightly

[bbb5317]

What version is this on? I tried with my current version but not working.

[xlionjuan]

@bbb5317 1.2.4 nightly