Skip to content

Security: dturovskiy/armactl

Security

SECURITY.md

Security Policy

Supported versions

Security fixes are expected only for the latest development state on main and the most recent published release, once releases exist.

Reporting a vulnerability

Please do not open a public GitHub issue for sensitive vulnerabilities.

Report security issues privately to the maintainer through GitHub contact channels. Include:

  • affected version or commit
  • environment details
  • reproduction steps
  • impact assessment
  • whether secrets, sudo rules, or system service behavior are involved

Security-sensitive areas

armactl interacts with:

  • sudo and systemd units
  • SteamCMD
  • runtime .env files for the Telegram bot
  • admin and RCON passwords
  • host logs and service output

When reporting or discussing bugs, redact:

  • passwordAdmin
  • game password
  • rcon.password
  • Telegram bot tokens
  • private IPs or hostnames when needed

Project posture

The project already aims to:

  • keep runtime .env files out of git
  • redact obvious secrets from logs and UI output
  • separate repo code, runtime data, and system service files

If you find a place where secrets leak or privileged behavior is too broad, please report it.

There aren't any published security advisories