Add resident $DATA of NTFS to tsk_file_layout #2871
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.
When using
loaddb
, all files of an NTFS file-system will be available on thetsk_file_layout
table. Except for resident-files, they are missing there. I noticed this while I was working with this table and needed to extract the location for all files.This PR adds those files to the
tsk_file-layout
-table, thebyte_start
&byte_len
will point directly to the resident$DATA
-buffer, thesequence
is always 0. This allows complete transparent processing of those file-layouts, including extractions of files from the image.It does this by calculating the offset in bytes relative to the start of the file-system (TSK_FS_ATTR.rd.offset) on NTFS file-systems. When I introduced new parameters to heavily used functions, I made an override for them to maintain compatibility.
This implementation works for my cases, I don't know if it works on all edge cases though.