@wdormann @0xabad1dea Unless it's data-driven and the bug was due to bad data? (e.g. fixed elsewhere?)
-
-
-
@raudelmil@0xabad1dea That's definitely not the case here. They are bugs found with our file fuzzer (FOE).
End of conversation
New conversation -
-
-
-
- 1 more reply
New conversation -
-
-
@wdormann@0xabad1dea I go to all that effort to fix bugs *and* find hash collisions, look at the thanks I get!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wdormann@0xabad1dea obviously they compiled it to always have the same MD5, using the latest techniquesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wdormann sounds like a fun way to troll. it's when it retains the same sha256 that you should be *really* pessimistic.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wdormann that's fixing bugs in style - change binary code AND produce an MD5 collisionThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.