Specify id/relay server as part of target id when connecting to another device (id@server)

[rustdesk]

Discussed in #2072

^{Originally posted by vladimir-angelov-1337 November 11, 2022}
It would be cool if instead of "123 456 789" I could write "123 456 789@domain.com" when connecting to another device and that would use domain.com as the id/relay server for this specific connection. That way even with self-hosted setups we could connect cross-organization.

[pedjas]

That way keys could be specified in domain DNS so clients would not have to bother with that too.

[vladimir-angelov-1337]

@rustdesk
Thank you!

@pedjas
Yes, exactly!

[ertankucukoglu]

I hope it will not be limited with domain and something like 123 456 789@1.1.1.1 would be possible. Not everybody uses a domain anyway.

I know there is IPv6 side of the things, though it would be considerable to start with IPv4

[pedjas]

I hope it will not be limited with domain and something like 123 456 789@1.1.1.1 would be possible. Not everybody uses a domain anyway.

Actually, domain part in ID does not have to be actual host address. It servers just as identification of a server. Client can check SRV record in domain DNS to see what is actual server address.

Fine example of using SRV records is in XMPP (Jabber) protocol. It allows everyone to run their own XMPP server but they can communicate with everyone else World wide as actual server for each user can be determined from DNS.

However both ways could be useful.

For example if @ is used as separator that could mean that server info should be taken from DNS. If # is used as separator that could mean actual address of server follows (which could be domain or plain IP).

Use DNS to get connection info:
123 456 789@mydomain.org

Connect directly to specified server:
123 456 789#rustdesk.mydomain.org
123 456 789#1.1.1.1

There is issue how to handle key if DNS is not used.

[vladimir-angelov-1337]

Can I put up a bounty for this?

[rustdesk]

Can I put up a bounty for this?

Of course, but check out this first, #1953

[vladimir-angelov-1337]

Does US$100 seem reasonable?

[pedjas]

Other way to resolve this is kid of like https does. Client connects to server without key. First thing server does is deliver the key to the client. Client then switches to secure connection using provided key.

This way, users would not bother with keys at all.

[rustdesk]

@Xerxes-2 this can be done together with #2058

[rustdesk]

The problem is how to pass the key in? Need extra UI to manage keys.

Usually users does not want to expose their keys, so do not ask why not fetch the key from the url (dns).

[rustdesk]

Combine this with #1873, no plan to implement solely. Discuss there please.

[rustdesk]

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