You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(core): exempt Zone.Identifier from the ads_skipped warning (#288)
`local.ads_skipped` fires for every file carrying a named NTFS stream,
because named streams are not backed up. But the overwhelmingly common
named stream is `Zone.Identifier` - the mark-of-the-web tag Windows
attaches to every downloaded file. It is transient browser provenance
metadata, not user data, and on a Documents tree full of downloads it
produced ~3,500 warnings per scan (14,098 of the 14,174 lines in the
2026-08-14 incident-day log), burying the useful signal.
This exempts it at the detection probe: a file whose **only** named
stream is `Zone.Identifier` is no longer flagged; any other named stream
still warns (with or without a Zone.Identifier alongside - the exemption
cannot mask real data). The check is free:
`FindFirstStreamW`/`FindNextStreamW` already return the stream names in
the enumeration the probe runs; this adds one ASCII case-insensitive
comparison, zero extra syscalls.
The chaos `ads-alternate-data-stream` scenario (`foo.txt:hidden`) is
unaffected and still asserts the warning for real streams. New
Windows-only unit test covers: no-stream and Zone-only files don't flag,
the exemption is case-insensitive (NTFS stream names are), a real named
stream flags, and Zone.Identifier next to another stream still flags.
Skips gracefully on a non-NTFS temp volume.
README checked - no changes needed (it does not enumerate per-file
warnings).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01A7q3CvJzL4zZmDA9CbXyQQ
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments