ci: security scanning, with the findings read and justified #3
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/webmin!3
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. semgrep's OSS
rules have no Perl, so most of Webmin is covered by gitleaks only.
Baseline from a scan of master, none a risk. bandit B202 and B113 in
buildsrc_lib, the maintainer's import tool: the release tarball is
extracted only after its GPG signature is verified, and a missing
timeout can only hang a download. semgrep: two bash best-practice
hits in update-from-repo.sh. shellcheck: 86 warnings of upstream's
setup.sh, update scripts and maintainer scripts, each justified in
.github/security-baseline.
gitleaks finds 21 hits in the history, none live: minified xterm.js,
translation strings, RFC 6455's WebSocket GUID, a PEM header string
in nginx-lib.pl, and upstream's public default miniserv.pem, imported
with the 2.102 source and removed on 2026-08-24. Ignored by
fingerprint in .github/.gitleaksignore.