feat/hash_passthrough #48
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
garrett/wafb!48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/hash_passthrough"
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?
🛠 Type of Change
📖 Description
What does this PR do?
Implementa un servizio di hashing in grado di accogliere uno streaming
Ci ho infilato inoltre diversi refactoring per migliorare l'architettura generale
🧪 Testing
pnpm test)pnpm lint)⚖️ Forensics Integrity Checklist
Implements incremental hashing as a TransformStream passthrough using hash-wasm. Memory usage is O(1) — each chunk is hashed in-place and forwarded immediately without buffering, making it safe for large streams (backups, dumpsys, etc.). - utils/stream-helpers.ts: add hashingPassthrough(algorithm) async fn returning { writable, readable, hashPromise }. Supports sha-1, sha-256, sha-512 via lazy WASM import. - tsup.config.ts: hash-wasm already in external (was pre-configured) - package.json / pnpm-lock.yaml: add hash-wasm ^4.12.0 dependency - backup.ts: first integration — wraps backup stream with passthrough when computeHash is true, attaches hashPromise to AcquisitionFile