anonymize breaks trace

#3 · closed · 2 comments

View on GitHub ↗

dominikh

``` $ go tool trace -d staticcheck.trace | wc -l 2023/04/15 04:10:12 Parsing trace... 277357 $ ./traceutils anonymize staticcheck.trace staticcheck.trace.anon $ go tool trace -d staticcheck.trace.anon | wc -l 2023/04/15 04:10:28 Parsing trace... failed to parse trace: unknown event type 55 at offset 0x1adcd2 0 ``` I've attached the original trace and the resultant anonymized trace. [staticcheck.trace.anon.gz](https://github.com/felixge/traceutils/files/11238086/staticcheck.trace.anon.gz) [staticcheck.trace.gz](https://github.com/felixge/traceutils/files/11238087/staticcheck.trace.gz)

Comments

felixge

Thanks for reporting this 🙇‍♂️. I started working on improving this code the other day and will take this issue into account!

felixge

This should be fixed now. Additionally anonymize is now more aggressive in order to prevent any potential reversing of the obfuscation. I also added a `strings` command to verify the output.