OLD | NEW |
1 ================== | 1 ================== |
2 american fuzzy lop | 2 american fuzzy lop |
3 ================== | 3 ================== |
4 | 4 |
5 Written and maintained by Michal Zalewski <lcamtuf@google.com> | 5 Written and maintained by Michal Zalewski <lcamtuf@google.com> |
6 | 6 |
7 Copyright 2013, 2014, 2015, 2016 Google Inc. All rights reserved. | 7 Copyright 2013, 2014, 2015, 2016 Google Inc. All rights reserved. |
8 Released under terms and conditions of Apache License, Version 2.0. | 8 Released under terms and conditions of Apache License, Version 2.0. |
9 | 9 |
10 For new versions and additional information, check out: | 10 For new versions and additional information, check out: |
(...skipping 172 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
183 Non-instrumented binaries can be fuzzed in the QEMU mode (add -Q in the command | 183 Non-instrumented binaries can be fuzzed in the QEMU mode (add -Q in the command |
184 line) or in a traditional, blind-fuzzer mode (specify -n). | 184 line) or in a traditional, blind-fuzzer mode (specify -n). |
185 | 185 |
186 You can use -t and -m to override the default timeout and memory limit for the | 186 You can use -t and -m to override the default timeout and memory limit for the |
187 executed process; rare examples of targets that may need these settings touched | 187 executed process; rare examples of targets that may need these settings touched |
188 include compilers and video decoders. | 188 include compilers and video decoders. |
189 | 189 |
190 Tips for optimizing fuzzing performance are discussed in perf_tips.txt. | 190 Tips for optimizing fuzzing performance are discussed in perf_tips.txt. |
191 | 191 |
192 Note that afl-fuzz starts by performing an array of deterministic fuzzing | 192 Note that afl-fuzz starts by performing an array of deterministic fuzzing |
193 steps, which can take several days. If you want quick & dirty results right | 193 steps, which can take several days, but tend to produce neat test cases. If you |
194 away, akin to zzuf or honggfuzz, add the -d option to the command line. | 194 want quick & dirty results right away - akin to zzuf and other traditional |
| 195 fuzzers - add the -d option to the command line. |
195 | 196 |
196 7) Interpreting output | 197 7) Interpreting output |
197 ---------------------- | 198 ---------------------- |
198 | 199 |
199 See the status_screen.txt file for information on how to interpret the | 200 See the status_screen.txt file for information on how to interpret the |
200 displayed stats and monitor the health of the process. Be sure to consult this | 201 displayed stats and monitor the health of the process. Be sure to consult this |
201 file especially if any UI elements are highlighted in red. | 202 file especially if any UI elements are highlighted in red. |
202 | 203 |
203 The fuzzing process will continue until you press Ctrl-C. At minimum, you want | 204 The fuzzing process will continue until you press Ctrl-C. At minimum, you want |
204 to allow the fuzzer to complete one queue cycle, which may take anywhere from a | 205 to allow the fuzzer to complete one queue cycle, which may take anywhere from a |
(...skipping 263 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
468 Richo Healey Martijn Bogaard | 469 Richo Healey Martijn Bogaard |
469 rc0r Jonathan Foote | 470 rc0r Jonathan Foote |
470 Christian Holler Dominique Pelle | 471 Christian Holler Dominique Pelle |
471 Jacek Wielemborek Leo Barnes | 472 Jacek Wielemborek Leo Barnes |
472 Jeremy Barnes Jeff Trull | 473 Jeremy Barnes Jeff Trull |
473 Guillaume Endignoux ilovezfs | 474 Guillaume Endignoux ilovezfs |
474 Daniel Godas-Lopez Franjo Ivancic | 475 Daniel Godas-Lopez Franjo Ivancic |
475 Austin Seipp Daniel Komaromy | 476 Austin Seipp Daniel Komaromy |
476 Daniel Binderman Jonathan Metzman | 477 Daniel Binderman Jonathan Metzman |
477 Vegard Nossum Jan Kneschke | 478 Vegard Nossum Jan Kneschke |
478 Kurt Roeckx | 479 Kurt Roeckx Marcel Bohme |
| 480 Van-Thuan Pham Abhik Roychoudhury |
479 | 481 |
480 Thank you! | 482 Thank you! |
481 | 483 |
482 15) Contact | 484 15) Contact |
483 ----------- | 485 ----------- |
484 | 486 |
485 Questions? Concerns? Bug reports? The author can be usually reached at | 487 Questions? Concerns? Bug reports? The author can be usually reached at |
486 <lcamtuf@google.com>. | 488 <lcamtuf@google.com>. |
487 | 489 |
488 There is also a mailing list for the project; to join, send a mail to | 490 There is also a mailing list for the project; to join, send a mail to |
489 <afl-users+subscribe@googlegroups.com>. Or, if you prefer to browse | 491 <afl-users+subscribe@googlegroups.com>. Or, if you prefer to browse |
490 archives first, try: | 492 archives first, try: |
491 | 493 |
492 https://groups.google.com/group/afl-users | 494 https://groups.google.com/group/afl-users |
493 | 495 |
494 PS. If you wish to submit raw code to be incorporated into the project, please | 496 PS. If you wish to submit raw code to be incorporated into the project, please |
495 be aware that the copyright on most of AFL is claimed by Google. While you do | 497 be aware that the copyright on most of AFL is claimed by Google. While you do |
496 retain copyright on your contributions, they do ask people to agree to a simple | 498 retain copyright on your contributions, they do ask people to agree to a simple |
497 CLA first: | 499 CLA first: |
498 | 500 |
499 https://cla.developers.google.com/clas | 501 https://cla.developers.google.com/clas |
500 | 502 |
501 Sorry about the hassle. Of course, no CLA is required for feature requests or | 503 Sorry about the hassle. Of course, no CLA is required for feature requests or |
502 bug reports. | 504 bug reports. |
OLD | NEW |