← Back to blog

QR codes and clipboard imports can expose server credentials

Share links and QR codes often contain server address, user ID, secret or subscription token. They are credentials, not harmless screenshots.

Steps

  1. Display a QR only on trusted devices in private. Screen sharing, livestream recording and automatic photo backup can copy it.
  2. After clipboard import, overwrite the clipboard with non-sensitive text; remember cloud clipboard and cross-device sync.
  3. Never post a complete share link in a forum. Preserve protocol and error fields but replace domain, UUID, password and local path.
  4. If exposure is possible, rotate UUID, password or token on the server and invalidate the old value. Local deletion does not revoke it.

Why this matters

Anyone holding the link may consume your quota and connect under your identity. Treating it like a password is cheaper than investigating abuse.

How to verify

Public screenshots and logs cannot reconstruct an endpoint or credential, and rotated links no longer connect.

Things to watch

Blurring a small QR area is unreliable because error correction may still recover the encoded data.

Official references

Latest security releaseUI security settings