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

Duplicate Event Tags in pinfo #1067

Closed
jamdunnDFW opened this issue Oct 24, 2016 · 3 comments
Closed

Duplicate Event Tags in pinfo #1067

jamdunnDFW opened this issue Oct 24, 2016 · 3 comments
Assignees
Labels
blocked Work cannot progress until another issue is resolved storage

Comments

@jamdunnDFW
Copy link

Plaso version:

Ubuntu Development Release 1.5.2_20161224

Operating system Plaso is running on:

Windows XP

Installation method:

Built using git clone https://github.com/log2timeline/plaso.git

Description of problem:

I ran two (slightly different) tagging analyses over the same storage file and found the number of event tags doubled when an entry was tagged twice with the same tag.

The output using psort de-duplicates fine and doesn't appear to cause any issues. The only thing that seems to be affected is the pinfo report "Event tags generated per label", which reports double the amount of tags that actually exist.

Not sure if this qualifies as an issue or something I should just not do again.

@joachimmetz joachimmetz added the blocked Work cannot progress until another issue is resolved label Oct 25, 2016
@joachimmetz joachimmetz self-assigned this Oct 25, 2016
@joachimmetz
Copy link
Member

How tags are currently stored are far from optimal. We are planning to overhaul this as part of #568

@jamdunnDFW
Copy link
Author

10-4, thanks for the update

@joachimmetz
Copy link
Member

Closing issue, it refers to the old ZIP based storage file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Work cannot progress until another issue is resolved storage
Projects
None yet
Development

No branches or pull requests

2 participants