ci: security scanning, with the findings read and justified #17
No reviewers
Labels
No labels
accessibility
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/buildtasks!17
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 19.x and by hand. Not a required check.
Baseline from a scan of 19.x, none a risk. bandit B103 and semgrep's
insecure-file-permissions: 0o750 on the root-owned EC2 user-data
script, 0o700 on ~/.ssh. Plus 205 shellcheck warnings of existing
scripts (arrays in log messages, word splitting of build paths, unused
config variables), each justified in .github/security-baseline.
Eight Python 2 scripts under bin/ec2_legacy and contrib cannot be
parsed by bandit and are reported as warnings.
gitleaks: tests/layer writes truncated fake key headers on purpose and
tests/ec2-v19 named public key fingerprints, allowlisted by path in
.github/gitleaks.toml; BT_GPGKEY and GPGKEY are fingerprints of the
public TurnKey signing keys, ignored by fingerprint in
.github/.gitleaksignore.