Direct connections possible on clients with different keys #3216

New issue

Closed

opened 2026-02-21 01:12:38 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 01:12:38 -05:00

Owner

Originally created by @delko-it on GitHub (Jan 6, 2025).

Bug Description

Direct connections are possible on two separate clients with different keys filled. Relayed connections return expected behavior - "deadline has elapsed" or "key mismatch".

How to Reproduce

Setup two clients in different networks. On first one set key 123456789, on second 0987654321. Try to connect relayed /r, you get "deadline has alapsed". When you try connecting directly, then direct encrypted connection pops up. I think that well known rustdesk public key is envolved.

Expected Behavior

Connection between clients with different keys not possible.

Operating system(s) on local (controlling) side and remote (controlled) side

Windows 10 -> Windows 11

RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.3.6 -> 1.3.6

Screenshots

Additional Context

No response

Originally created by @delko-it on GitHub (Jan 6, 2025). ### Bug Description Direct connections are possible on two separate clients with different keys filled. Relayed connections return expected behavior - "deadline has elapsed" or "key mismatch". ### How to Reproduce Setup two clients in different networks. On first one set key 123456789, on second 0987654321. Try to connect relayed /r, you get "deadline has alapsed". When you try connecting directly, then direct encrypted connection pops up. I think that well known rustdesk public key is envolved. ### Expected Behavior Connection between clients with different keys not possible. ### Operating system(s) on local (controlling) side and remote (controlled) side Windows 10 -> Windows 11 ### RustDesk Version(s) on local (controlling) side and remote (controlled) side 1.3.6 -> 1.3.6 ### Screenshots ![direct-different-keys](https://github.com/user-attachments/assets/532e6bab-e1ba-420a-9321-d0db217bd667) ### Additional Context _No response_