ci: security scanning, with the findings read and justified #13
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/keel-redis!13
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.
A scan of master finds no Python and nothing for semgrep or shellcheck.
gitleaks flags KEEL_APT_KEY in the Makefile, the OpenPGP fingerprint of
the archive staging signing subkey: public by design, allowlisted by
value in .github/gitleaks.toml. The other two hits, curl --user admin:fixture in
tests/v19-upgrade.sh (since removed), are a throwaway test login,
allowlisted by path.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.