Skip to content
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

Parsers should filter out events that appear to have occurred at relevant epoch(s)? #920

Closed
ghost opened this issue Aug 13, 2016 · 1 comment
Assignees
Labels
duplicate Duplicate of another issue enhancement New or improved functionality

Comments

@ghost
Copy link

ghost commented Aug 13, 2016

1.5 RC1 GIFT PPA Ubuntu 14.04 LTS 64 bit

Evidence image: http://www.lancemueller.com/blog/evidence/WinXP2.E01

log2timeline with default options && psort.py -w output.txt results.plaso

winreg/appcompatcache generates events on date 1601-01-01

winreg/windows_version and msiecf generate events on date 1970-01-01

These parsers appear to be misinterpreting missing/null timestamps and converting them to dates that match the relevant epochs. It is unlikely that the activity occurred on those dates - such results could be used to cast doubt on accuracy of parsing.

@joachimmetz joachimmetz added duplicate Duplicate of another issue enhancement New or improved functionality labels Aug 13, 2016
@joachimmetz joachimmetz self-assigned this Aug 13, 2016
@joachimmetz
Copy link
Member

joachimmetz commented Aug 13, 2016

This is a known issue. We are planning to address this by: #910.

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate of another issue enhancement New or improved functionality
Projects
None yet
Development

No branches or pull requests

1 participant