-
Notifications
You must be signed in to change notification settings - Fork 203
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
Result files are not the same when running csv(json)-timeline command multiple times #1466
Comments
The only difference seems to be the count rules. |
I think this is because we are not sorting events anymore so the events that hayabusa sees (and outputs) are random each time. So that might be why the order of usernames is not the same. What do you think? |
@YamatoSecurity
Yes, the default is not to sort by timestamp, but the expectation is that it will be the same every time, even without the -s option! (That is the behavior until before the 2.18.0 release🤔) |
(It is not a bug since it is not a stated specification, but it is better to have no differences when testing) |
@fukusuket I see. That is a good point. What about sorting the count results ( |
You read my mind! 😆 #1467 |
Removed bug tags from issues (added enhancement tags instead), as without the -s option, the spec behavior is to not sort. |
Describe the bug
Result files are not the same when running csv(json)-timeline command multiple times :(
Step to Reproduce
./hayabusa-2.18.0-mac-aarch64 csv-timeline -d ../hayabusa-sample-evtx -w -1.csv
./hayabusa-2.18.0-mac-aarch64 csv-timeline -d ../hayabusa-sample-evtx -w -2.csv
Actual behavior
Result files are different each time.
Expected behavior
Result file is the same every time.
Environment
Additional context
Same number of detections, just different sort order.
Until recently, there was no diff, so the library update may have changed the behavior? 🤔
The text was updated successfully, but these errors were encountered: