-
-
Notifications
You must be signed in to change notification settings - Fork 4
Step 14b/23 (Phase 3): Signatures — Implement ClamAV hash-only signature fetcher #161
Copy link
Copy link
Open
Labels
area:signaturesSignature sources / licensingSignature sources / licensingdifficulty:intermediateModerate complexityModerate complexityphase:3-updates-signaturesUpdates & signatures (Steps 13–14)Updates & signatures (Steps 13–14)priority:p0Critical path / blockingCritical path / blockingtrack:post-mvpDeferred until after the MVP demo; still aligned with the 2026 plan end goalsDeferred until after the MVP demo; still aligned with the 2026 plan end goals
Milestone
Description
Metadata
Metadata
Assignees
Labels
area:signaturesSignature sources / licensingSignature sources / licensingdifficulty:intermediateModerate complexityModerate complexityphase:3-updates-signaturesUpdates & signatures (Steps 13–14)Updates & signatures (Steps 13–14)priority:p0Critical path / blockingCritical path / blockingtrack:post-mvpDeferred until after the MVP demo; still aligned with the 2026 plan end goalsDeferred until after the MVP demo; still aligned with the 2026 plan end goals
Summary
Implement a Python script that fetches ClamAV signature databases, extracts hash-only signatures using `sigtool`, and outputs them in the project's normalized format.
Depends On: Step 14a (Licensing matrix — ClamAV must be approved)
Parent Issue: #12 (Integrate Real-World Malware Signatures)
Context
ClamAV provides `main.cvd` and `daily.cvd` signature databases under GPL-2.0. Using `sigtool --list-sigs`, we can extract MD5 and SHA1 file hashes without redistributing the full ClamAV database.
Key Changes
Acceptance Criteria