Path resolution policy #46
Miauwkeru
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Starting from Dissect version 3.11, the policy is for plugins to only provide the original parsed
pathvalue in returned records.We recommend external contributors to follow the same policy, this keeps the path information in the records as close to the truth as possible.
Resolved paths can be accessed by using the
--resolveor--hashflags intarget-query.These flags add additional fields to the record using the name of the field as a prefix making it easier to identify its origin.
For example, lets say we have a record with the following field:
When using
--resolve, the resolved path will be added to the record in a new field with the suffix_resolved:The
--hashflag extends the--resolveinformation and includes a_digestsuffixed field as well, which contains the file digest triple (if the file exists):Beta Was this translation helpful? Give feedback.
All reactions