Repository navigation
Read the NTFS $LogFile (restart areas and log records, as recorded) - #168
Merged
Merged
Conversation
Part of #57, at a conservative scope: restart areas, log record headers and redo/undo operations, target attribute fields, and names with timestamps only where the payload is a plain $FILE_NAME or index entry. No timeline is reconstructed. Adds the artefact route and viewer, a synthetic $LogFile builder and a fuzz target. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017DPjyZZHvaivtvJ3N4hZhz
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #57, at the conservative scope agreed.
What it does
New artefact NTFS log (Artefacts → route
/api/logfile, viewer with filter and paging):$FILE_NAMEpassing length/time/character checks.Deliberately not done
No reconstruction of events or timeline (the log is a ring; an inferred story could mislead), no target MFT record number, no names from whole-MFT-record payloads. Noted in ROADMAP.
Verification — please read
logfile.hand the walking approach of third-party parsers. There is no real$LogFilein the repository or available to me, so this is tested on synthetic logs only (new builderimagebuild_logfile.py, which is written from the format description rather than the parser). Uncertain points (record continuation across pages,next_record_offsetsemantics) follow those sources and need checking against a real log.🤖 Generated with Claude Code
https://claude.ai/code/session_017DPjyZZHvaivtvJ3N4hZhz
Generated by Claude Code