ci: security scanning, with the findings read and justified #32
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/confconsole!32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/security-scan"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Calls security-scan.yml of keel-linux/.github (gitleaks, bandit,
semgrep, shellcheck on hosted runners, no secrets) on pull requests,
pushes to master and by hand. Not a required check.
Baseline from a scan of master, none a risk. bandit B605 and semgrep's
tainted-env rule on the same line: os.system of a constant shutdown
command, prefixed by chvt $FGVT from confconsole's own environment, a
root process. B104: WILDCARDS recognises a wildcard listen address, it
binds nothing. B113: a request with no timeout can only hang the
Let's Encrypt dialog. semgrep's insecure-file-permissions: only the
execute bits of two root-owned scripts are toggled. Plus 15 shellcheck
warnings of existing scripts.
gitleaks: the WireGuard keys of two test files are fixtures,
allowlisted by path in .github/gitleaks.toml.