Repository navigation
feat: daily external port scan of spore - #748
Merged
Merged
Conversation
A GitHub runner scans every TCP port on spore's public address and posts to #alerts if one is open that spore's firewall on main doesn't allow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
.github/workflows/port-scan.yml. Once a day, a GitHub runner, outside every network spore trusts, connect-scans all 65535 TCP ports on spore's public address withnmap. It fails and posts to #alerts (throughstackptr/actions/slack-notify) when:networking.firewallon main doesn't allow: an undeployed or reverted change, a rule outside the NixOS firewall, or something at CloudCone; orThe address and the allowed ports both come from evaluating spore's config, so nothing needs updating by hand. The workflow also runs on PRs that touch it, with Slack in dry-run mode, so this PR's own run tests it.
Scope: spore only. Home's public IPv4 is dynamic and isn't in the repo, so there's no stable target to scan. The only home exposure is glyph's 53150 forward, and home has no global IPv6.
To verify:
Port scanrun showsOpen: 22 80 443 6697(or a subset) and passes, in a few minutesgh workflow run port-scan.yml🤖 Generated with Claude Code