Colony Firewall Control is alpha software. It runs a daemon as root with CAP_NET_ADMIN and makes allow/deny decisions about your network traffic, so security reports are taken seriously -- but expectations should match the project's maturity: there has been no external audit, and interfaces may change without notice.

Only the latest release and the current main branch receive security fixes. Older releases are not supported; upgrade before reporting.

Please report vulnerabilities privately via GitHub's security advisory form for this repository:

• Go to the repository's Security tab -> Report a vulnerability, or use https://github.com/Project-Colony/Colony-Firewall-Control/security/advisories/new

Please do not open a public issue for anything you believe is exploitable (privilege escalation via the daemon, rule-bypass of the NFQUEUE filter, crafted-packet parsing crashes, socket permission problems, etc.).

What to expect:

• This is a single-maintainer hobby project; acknowledgement is best-effort, usually within a week.
• If the report is accepted, a fix will be worked on for the next release and you will be credited in the advisory unless you prefer otherwise.
• If it is declined, you will get a short explanation.

Dependency vulnerabilities are scanned continuously in CI with cargo deny (RustSec advisory database); a report is still welcome if you spot an exploitable path through a dependency before CI does.