-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MFT Parser usage or bug? #556
Comments
Could you run the first example with -d, and paste some of the output? |
Try the parser named |
Sorry, mtu was a typo since I hand copied it over and it was supposed to be mft. I ran the following command (copy/paste this time) and it had 0 results.
|
I ran this next.
|
Ack, thanks for reaching out and confirming. This appears to be an issue in the parser selection for file system metadata files. We'll have a look creating a fix. |
Thanks for confirming I'm not going crazy and can't wait to see the fix. Great tool and I really appreciate the time everyone has put into making it work. |
Can you try the current development version. |
I tried the recent development version and it did not work on an image file but did work on a MFT file. I've attached the log file. commands:
|
Thanks for checking, apparently still some more changes in the parser selection are needed. |
Changes are in, reopen the issue if needed. |
Any ETA on the push for this into the github since codereview was 23 days ago? |
@marcurdy what do you mean by "push" ? the last changes are merged with HEAD 23 days ago? What does an ETA (of what?) is going to tell you? |
Hello,
When using just the mft parser against a .vmdk file it returns no results but when run against the extracted $MFT file from that same image it returns ~550MB of results (l2t csv format). This is using the Plaso 1.4 and only the "mft" parser
Examples:
No Results example:
log2timeline.exe -p --partition all --vss_stores all --parsers mft --workers 5 tmp.db "E:\tmp.vmdk"
Restults examples:
log2timeline.exe -p --parsers mft --workers 5 tmp.db "E:\extracted_data$MFT"
Is this how it is supposed to work or is this a bug?
The text was updated successfully, but these errors were encountered: