News for hackers. Stuff that matters.

A comment on Vectorized Emulation: fuzzing at 2 trillion instructions per second. Parent comment

Re:Vectorized Emulation: fuzzing at 2 trillion instructions ... by trishume on Wednesday October 17, 2018 @12:06PM (#18240402)
I bet his mutation strategy works in tandem with the SIMD strategy. Probably the input for each SIMD lane differs by only one byte or something so that they are maximally coherent.
[ Parent | on HN ]
Re:Vectorized Emulation: fuzzing at 2 trillion instructions ... by gamozolabs on Wednesday October 17, 2018 @02:44PM (#18242292)
Bingo
[ Parent | on HN ]
Re:Vectorized Emulation: fuzzing at 2 trillion instructions ... by TickleSteve on Wednesday October 17, 2018 @02:58PM (#18242479)
So what you're really doing is (in parallel) finding the decoherence points... These branching/decision points are much more easily found by instrumenting the code as in AFL.

No need to parallelise at all, the compiler gives you that information.

What you have seems like a neat trick, but not an efficient way of actually fuzzing.

[ Parent | on HN ]
Re:Vectorized Emulation: fuzzing at 2 trillion instructions ... by dragontamer on Wednesday October 17, 2018 @04:10PM (#18243268)
> compiler gives you that information

It seems like he's fuzzing machine code. So he doesn't have the original source code.

[ Parent | on HN ]