Skip to content

Conversation

@mikungg
Copy link

@mikungg mikungg commented Dec 9, 2025

Before the fix:
image

After the fix:
image

I assume the problem was because the time_offset is undefined
image

So we need to makes sure we read for the timezone (and set it to UTC if no timezone is found just in case)
image

Turns out the timezone is America/New_York, this concludes the reader works properly
image

The image used for the testing:
https://digitalcorpora.s3.amazonaws.com/corpora/scenarios/magnet/2020%20CTF%20-%20Android.tar

@stark4n6
Copy link
Collaborator

stark4n6 commented Dec 9, 2025

@mikungg in my opinion, we shouldn't be setting the offset from the timezone from here because it could hold multiple values, we want to set every timestamp to uniform UTC. The timezone_offset was a configurable feature that we are phasing out of but regardless the parser needs to be fixed to account for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants