@@ -94,8 +94,7 @@ For more information, see
94
94
95
95
In FRIDA mode, you can fuzz binary-only targets as easily as with QEMU mode.
96
96
FRIDA mode is most of the times slightly faster than QEMU mode. It is also
97
- newer, lacks COMPCOV, and has the advantage that it works on MacOS (both intel
98
- and M1).
97
+ newer, and has the advantage that it works on MacOS (both intel and M1).
99
98
100
99
To build FRIDA mode:
101
100
@@ -113,10 +112,6 @@ The mode is approximately 2-5x slower than compile-time instrumentation, and is
113
112
less conducive to parallelization. But for binary-only fuzzing, it gives a huge
114
113
speed improvement if it is possible to use.
115
114
116
- If you want to fuzz a binary-only library, then you can fuzz it with frida-gum
117
- via frida_mode/. You will have to write a harness to call the target function in
118
- the library, use afl-frida.c as a template.
119
-
120
115
You can also perform remote fuzzing with frida, e.g., if you want to fuzz on
121
116
iPhone or Android devices, for this you can use
122
117
[ https://github.com/ttdennis/fpicker/ ] ( https://github.com/ttdennis/fpicker/ ) as
@@ -302,7 +297,6 @@ some are very hard to set up...
302
297
* S2E: [ https://github.com/S2E ] ( https://github.com/S2E )
303
298
* TinyInst:
304
299
[ https://github.com/googleprojectzero/TinyInst ] ( https://github.com/googleprojectzero/TinyInst )
305
- (Mac/Windows only)
306
300
* ... please send me any missing that are good
307
301
308
302
## Closing words
0 commit comments