Skip to content

Security: b3p3k0/SWLer

SECURITY.md

Security

Deployment boundary

SWLer has no accounts, authorization layer, or built-in HTTPS. It binds all interfaces by default so phones on the same network can reach it. Do not expose port 8073 to the public internet.

Use a trusted LAN or Tailscale. Keep rigctld bound to 127.0.0.1; its protocol has no useful authentication.

SWLer's radio client is deliberately receive-only. Its typed allowlist covers tuning, passband, receive gain/filter controls, and read-only status. There is no raw-command endpoint or transmit path.

Reporting a vulnerability

Please use GitHub private vulnerability reporting for security issues. Do not post exploit details in a public issue.

Ordinary bugs and feature requests can use the issue tracker.

There aren't any published security advisories