Skip to content

Security: Prabotics/RapiDrop

Security

SECURITY.md

Security Policy

RapiDrop is designed from the ground up for private, local network operation without external cloud servers or tracking.

Security Model

  1. Local Network Boundary:
    • The application communicates strictly over your local Wi-Fi subnet via mDNS discovery and direct TCP connections.
    • Traffic never leaves the local subnet; no cloud relays, analytics, or external telemetry are used.
  2. Payload Encryption:
    • Payloads are encrypted using AES-256-GCM with fresh ephemeral session keys negotiated per connection.
    • Every transmitted frame uses a unique 96-bit random nonce and a 128-bit authentication tag.
  3. Password Manager Protections:
    • macOS: Clips flagged with org.nspasteboard.TransientType, org.nspasteboard.ConcealedType, or org.nspasteboard.AutoGeneratedType are dropped immediately.
    • Android: Clips flagged with ClipDescription.EXTRA_IS_SENSITIVE are dropped immediately.
    • Windows: Clips flagged with ExcludeClipboardContentFromMonitorProcessing, CanIncludeInClipboardHistory, or Clipboard Viewer Ignore are dropped immediately.

For technical cryptographic specifications and threat models, see docs/developer/security.md.

Reporting a Security Vulnerability

If you identify a security issue or cryptographic defect in RapiDrop:

  1. Do not open a public GitHub issue.
  2. Submit a private vulnerability report via GitHub Security Advisories on the repository: https://github.com/Prabotics/RapiDrop/security/advisories.
  3. Please include:
    • Description of the issue.
    • Affected platform (macOS, Android, Windows, or protocol specification).
    • Step-by-step reproduction steps or proof of concept.
    • Suggested remediation if available.

There aren't any published security advisories