-
Notifications
You must be signed in to change notification settings - Fork 205
Maite modules batch 2 #1301
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
base: main
Are you sure you want to change the base?
Maite modules batch 2 #1301
Conversation
Minor adjustments were made to timestamp handling and source path reporting.
Updated the query to select the raw time value instead of converting it to datetime in SQL. The conversion to UTC datetime is now handled in Python using convert_unix_ts_to_utc.
|
a couple things:
|
|
i don' have any test data for AMDSQLiteDB |
|
you can see there are some hits in test images here: https://github.com/abrignoni/iLEAPP/blob/main/admin/docs/filepath_search_summary.md |
|
Thanks for the link! Okay, so I think I'm just missing a step here. I can see the markdown file lists all the important file paths, but where do I find the actual test images or zips that have those files inside them? |
|
with the US Gov shutdown, some websites arent loading :( here are a few pages that have lists of test images.
@stark4n6 any other suggestions since NIST is currently down? |
|
@JamesHabben let me look, I think I made this parser so I think I actually had test files (either on my own test devices or from a sample) |
|
Most of these changes are pretty straight forward. The only parts that concern me are the dates to ensure we are using the correct function based on the source data. Once that is validated, I think this PR is good to merge. |
Refactoring: Timestamps and Argument Handling
This PR introduces two primary updates:
datetime(time/1000,'unixepoch')) from the query. Instead, we now pull the raw Unix timestamp and useconvert_unix_ts_to_utc()in Python. Is this the approach we should use?