Feat connect to peer on another server

[sahilyeole]

Still working

#6198 (comment)
Currently, I'm able to connect a peer on the public server while the control side is connected to a private server.
Support for public -> private in progress.

Ex: 143242314@164.432.413: 21116?key=32432432Efdsf34 or 143242314@public

cc.mp4

[sahilyeole]

@rustdesk How can I know which public server the peer is connected to?
Currently, I have hardcoded it just for testing.
Or else I can loop and try every public server available when user provides @public.

---

Also with current implementation, I'm getting the unencrypted connection. How can I encrypt it?

[rustdesk]

that is you need to figure out

[rustdesk]

public

You need to take care of this case https://rustdesk.com/docs/en/self-host/client-configuration/hardcode-settings/

[rustdesk]

No need to take care of multiple public servers, just use the first one, in the future we will use only one.

[sahilyeole]

No need to take care of multiple public servers, just use the first one, in the future we will use only one.

Ok so I'm currently using rs-ny.rustdesk.com:21116 server for @public. Is that enough?

[sahilyeole]

I have added support to get the private server key from the text field but I'm getting this error on connecting:

as connection to private servers requires login credentials of the user allowed on that server.

So I can try to support this text field expression:
Ex: 143242314@164.432.413:21116?key="32432432Efdsf34"?username="admin"?password="admin1234"
and authenticate the user for that server only for this particular connection.

Also, according to this, I think adding user credentials for the text field expression might be good. #6198 (comment)

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...

Should we try this?

[rustdesk]

No need to take care of multiple public servers, just use the first one, in the future we will use only one.

Ok so I'm currently using rs-ny.rustdesk.com:21116 server for @public. Is that enough?

Can not be hard coded, it may change in the future.

[rustdesk]

Should we try this?

No

[rustdesk]

as connection to private servers requires login credentials of the user allowed on that server.

Expected, no need to consider for now.

[rustdesk]

Also make sure 143242314@164.432.413:21116?key=32432432Efdsf34 works for uri, e.g. rustdesk://143242314@164.432.413:21116?key=32432432Efdsf34. and correctly saved in recent sessions

[sahilyeole]

• Used RENDEZVOUS_SERVERS to get public server
• URL connection done on macos. Windows & linux yet to check
• Private -> public still working on the encryption part

[rustdesk]

I will take over this issue. Please do the others