Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 9, 2026

Documentation Fix - Host Gateway Port Restrictions

This PR corrects inaccurate documentation that claimed v0.13.13 includes port restrictions for --enable-host-access. The security fix (commit 12683ac) referenced in the previous docs sync (#561) is not yet merged to main, so all ports are currently accessible when host access is enabled.

Changes Made

Updated docs/usage.md:

  • Fixed security warning to emphasize that ANY port is currently accessible with --enable-host-access
  • Documented --allow-host-ports as the proper way to restrict access
  • Added forward-looking note about future default port restrictions
  • Removed premature version-specific claims (v0.13.13+)

Code Changes Referenced

  • f84db28 (Feb 6): Previous docs sync that prematurely documented unreleased feature
  • 12683ac (unmerged): The actual security fix for port restrictions (still on branch fix/host-gateway-port-restriction)

Verification

  • ✅ Checked current code in containers/agent/setup-iptables.sh confirms no port restrictions
  • ✅ Documentation now accurately reflects actual v0.13.13 behavior
  • ✅ Forward guidance provided for users about upcoming changes

AI generated by Documentation Maintainer

Corrects inaccurate documentation that claimed v0.13.13 includes
port restrictions for --enable-host-access. The security fix
(commit 12683ac) is not yet merged to main, so all ports are
currently accessible when host access is enabled.

Changes:
- Update security warning to emphasize ANY port is accessible
- Document --allow-host-ports as the way to restrict access
- Add note about future default port restrictions
- Remove premature version-specific claims

This aligns documentation with actual code behavior in v0.13.13.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-generated documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant