flock_tap: audit-integrity + data-minimization for cloud-vs-local verdicts #3
Reference in New Issue
Block a user
Delete Branch "Trilltechnician/Flock_SCAN-fix:pr3-audit-integrity"
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?
Makes the passive tap a defensible auditing instrument for the cloud-vs-local question while shrinking what it retains about bystanders. Nothing here widens third-party capture.
What changed
_classify()folds flow-stat and device-level signals into exactly one of CLOUD_CONNECTED / LOCAL_STATION / INDETERMINATE;classify_device/classify_cameraare thin wrappers. The old divergent return sets fell out of summary buckets so totals never reconciled.counts_reconcileasserts cloud+local+indeterminate == total_ips_tracked.CLOUD_IP(...)evidence plus aTLS_CATEGORY(...)fallback; no unexplained verdict.max_samples(default 500,--tap-max-samples); exact integer counters stay precise past the cap.--tap-redact-ipssalt-hashes non-Flock destination IPs (known-Flock IPs stay legible).destination_summaryper cloud device (DNS names, TLS SNIs, known-Flock IPs) — who it talks to, never payload contents.Tests extend the merged suite (39 pass): vocabulary agreement, bucket reconciliation, indeterminate counting, CLOUD_IP evidence, sample capping vs exact counters, FRP descriptor, IP redaction, metadata-only summary. Stale-vocabulary assertions updated to INDETERMINATE.
Stacked on the merged #1/#2; base = main.
hell yee ninja lfg thank you!!