Skip to content

Security: aidanc/fcusb

SECURITY.md

Security reports

Only the current experimental source branch is maintained; no response-time or individual recovery commitment is offered. Treat USB/SCSI responses and image files as untrusted. Do not run arbitrary commands or change Windows security settings to overcome an identity or hash rejection.

Use GitHub's private vulnerability reporting, when enabled, via the repository Security tab → Report a vulnerability. If that option is unavailable, open a minimal issue requesting a private channel without exploit details, secrets, proprietary files or personal data. Do not invent or use an unofficial email address. Include affected public commit and a device-free reproduction where possible; do not publish weaponized hardware-damaging tests.

Payload-redacted logs can still contain paths and identifiers. Manually redact these before sharing. No telemetry or remote acknowledgement is implemented.

There aren't any published security advisories