fix: require complete image malware scans #127
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!127
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/clamav-complete-image-gate"
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?
Base-images PR #56 exposed a false green: the Zarf-agent image exceeded ClamAV MaxScanSize, but its incomplete scan remained a nonblocking warning and the image gate passed. This makes incomplete full-image scans fail, matching the existing application-layer requirement. Missing signatures, export/engine errors, timeouts and exceeded limits cannot produce clean or reusable evidence; partial malware detections still block. Reports distinguish blocking image diagnostics from the unchanged source warnings.
Increase the bounded expanded-content budget from 2000M to 4096M for clamscan and clamd. MaxFileSize remains 2000M; the existing image file/total/export caps, two workers and bounded batches remain intact. MaxScanSize counts recursively expanded content separately from input size. No approved vulnerability selector or workflow/job/status name changes.
Validation: 41 focused scanner/report tests pass in WSL; the real Trivy converter test is deferred to Library checks because pinned Trivy is not installed locally. The existing scaffold check passes all 16 mocked cases. Ruff fatal/undefined-name checks, diff checks and the active Gitleaks commit hook pass. A broader local suite could not pass in this Windows/WSL environment: missing defusedxml, Windows-linked Git metadata, and NTFS permission-mode assertions. Hosted Library checks remain required.
After review, publish/promote the library and rerun base-images PR #56 at its reviewed head. Acceptance still requires a clean Zarf-agent ClamAV record, zero malware warnings, a completed SBOM and zero blocking findings/scanner errors. The raised budget has not yet been validated against the real candidate.
Addresses Homelab/base-images#56 (comment)
Reviewed the authenticated current head
1aa47f9cb3. Image ClamAV setup retains bounded input/export/batch limits and applies the 4096M expanded-content limit in both standalone and daemon modes. Image database, scan/limit, export and timeout failures now produce an incomplete record plus a blocking scanner error rather than reusable clean evidence; partial detections remain blocking findings. The final decision fails on scanner errors, while source-only operational warnings remain advisory. Focused tests cover those paths and SBOM conversion remains a required follow-up. No UDS resource or routing changes are present. Source approval only: Workflow acceptance, Repository security and Library checks are still pending, and the raised limit has not been validated against the actual base-images Zarf-agent candidate. Do not merge or promote on this approval alone; require successful exact-head checks and a separate candidate-image scan before claiming the original case resolved.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.