ci: security scanning, with the findings read and justified #2
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/tklbam!2
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/B602 and
semgrep's tainted-env rules are in the bundled pylib, whose helpers run
the caller's own command with quoted arguments. mysql.py's shell=True
runs a constant mysql or mysqldump command with debian.cnf. SHA-1 is
an integrity check and fingerprint inside the escrow key packet (the
passphrase key is iterated SHA-256), or shapes random bytes; the
"shadow file" hits are regtest passwd and group files with x
placeholders; the file modes flagged are 0600, 0700 and 0750. Plus 17
shellcheck warnings of existing scripts.
bandit cannot parse 39 files, which are Python 2. gitleaks:
dep-commit-ids lists git commit ids, ignored by fingerprint in
.github/.gitleaksignore.