Skip to content

Conversation

@glamberson
Copy link
Contributor

Per MS-RDPECLIP sections 2.2.4.6 and 2.2.4.7, the Local Clipboard
Owner may lock the Shared Clipboard Owner's clipboard data before requesting
file contents to ensure data stability during multi-request transfers.

This enables server implementations to safely request file data from clients
when handling clipboard paste operations.

Changes

  • SendLockClipboard / SendUnlockClipboard message variants in ClipboardMessage
  • lock_clipboard() / unlock_clipboard() methods on Cliprdr<R>
  • Server handler wiring

Dependencies

Depends on #1063 (reqwest feature fix) to compile.

The server uses `ironrdp_tokio::reqwest::ReqwestNetworkClient` in
accept_credssp but the reqwest feature was not enabled, causing
compilation to fail.

Fixes Devolutions#1062
@glamberson glamberson force-pushed the pr1-clipboard-lock-unlock branch 3 times, most recently from 6eb562c to 0c8a574 Compare December 23, 2025 11:50
Per MS-RDPECLIP sections 2.2.4.6 and 2.2.4.7, the Local Clipboard Owner
may lock the Shared Clipboard Owner's clipboard data before requesting
file contents. This ensures data stability during multi-request file
transfers.

Adds lock_clipboard() and unlock_clipboard() methods with corresponding
ClipboardMessage variants for server integration.
@glamberson glamberson force-pushed the pr1-clipboard-lock-unlock branch from 0c8a574 to c455f2e Compare December 23, 2025 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants