Skip to content

Security: byebyebryan/remote-chrome

SECURITY.md

Security Policy

Supported Versions

Security fixes are made on the latest main branch; older commits and historical tags are not maintained release lines. Report the exact Git commit on both hosts. The launcher's --version string is diagnostic metadata and does not identify every fix on main.

Reporting a Vulnerability

Please do not open a public issue for a suspected vulnerability. Use GitHub's private vulnerability reporting instead.

Include the affected commit, local and remote Linux distributions, the command or configuration involved, expected and actual behavior, security impact, and a minimal reproduction when possible. Remove hostnames, usernames, SSH material, hardware-token secrets, and other sensitive data from reports.

Security-sensitive areas include:

  • SSH command and tunnel construction
  • USB/IP network exposure
  • YubiKey device selection, binding, attachment, and cleanup
  • local and remote sudo boundaries
  • lifecycle state and process ownership
  • the filtered browser bus and Secret Service ownership
  • notification name ownership, relay sockets, untrusted payload handling, reverse-forward construction, and session-scoped action/close callbacks

Reports will be acknowledged as soon as practical. Validation and remediation timelines depend on severity and reproducibility.

There aren't any published security advisories