if the given evtx folder has a corrupt file, chainsaw 2.2 will fail without telling me, at which file it got stuck. So I don't have a chance to fix it by hand or deleting the file in question.
I used chainsaw 1.1.4 to find the offending file, the error message there outputs the path :D.
In my case, the file was just empty. So maybe a "is file empty"-check before deserialization would make it a bit more robust?
Hey guys,
if the given evtx folder has a corrupt file, chainsaw 2.2 will fail without telling me, at which file it got stuck. So I don't have a chance to fix it by hand or deleting the file in question.
I used chainsaw 1.1.4 to find the offending file, the error message there outputs the path :D.
In my case, the file was just empty. So maybe a "is file empty"-check before deserialization would make it a bit more robust?
Thanks, Matthias