rustdesk / rustdesk/rustdesk-server-pro

[Feature Request/Regression] Log clipboard file transfers in Audit Logs (Pro Version)

Open
#932 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
317
Forks
119
PR merge metrics
No merged PRs in 30d

Description

In recent versions of RustDesk Server Pro, there is a discrepancy in how file transfers are logged. While using the dedicated "File Transfer" window correctly logs every transaction in the Web Dashboard's Audit Logs, performing a file transfer via Copy-Paste (Clipboard) does not trigger a log entry.

For IT administrators managing many endpoints (100+), it is critical for security and compliance to have a complete trail of all files entering or leaving a remote machine, regardless of the method used.

I would like to see clipboard-based file transfers integrated into the same logging system as the manual File Transfer module. If a file is copied from the local machine and pasted onto the remote machine (or vice-versa),

We are using the RustDesk Server Pro (v1.7.7) and noticed that this behavior changed compared to older versions. Keeping a full audit trail is a key reason we chose the Pro version, and having "invisible" file transfers through the clipboard is a security gap for our organization.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository file, test, or entry point. Start by tracing how clipboard transfers and dedicated file transfers reach the Pro audit-log path; completion means both local-to-remote and remote-to-local clipboard transfers produce audit entries.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.