stdman
American Fuzzy Lop
Our great sponsors
stdman | American Fuzzy Lop | |
---|---|---|
1 | 21 | |
914 | 2,903 | |
- | - | |
1.8 | 0.0 | |
over 1 year ago | almost 3 years ago | |
C++ | C | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stdman
-
Creating Info Manuals And Adding Them Into Emacs
neat! reminds me of stdman which is wonderful to access from emacs as well. Does anybody else generate info manuals for stuff besides the python std library example in this post?
American Fuzzy Lop
-
Prefer table driven tests (2019)
There's some efforts to guide test generation for property based testing to make the instruction pointer explore as large a space as possible.
This effort is more mature in the fuzzing community. See eg American Fuzzy Lop https://github.com/google/AFL
-
C++ Faker library
What you're describing, just generating random input to test a program, is sometimes called "blind fuzzing" but the state-of-the-art is far beyond that. Maybe try reading through the documentation of e.g. https://github.com/google/AFL to see what a fuzzer does and why just producing random input isn't even scratching the surface.
-
Hyperpom: An Apple Silicon Fuzzer for 64-bit ARM Binaries
for general riscv I used to use this https://github.com/google/AFL I dont know if it supports x64 tho.
-
How to fuzz java code with jazzar?
Ex ( AFL, WinAFL, HonggFuzz, LibFuzzer, Jazzer )
-
One year ago I wrote a buddy memory allocator - project update
I wrote this little fuzz test target in order to fuzz it with afl (under ASan and UBSan):
-
Beariish/little: A small, easily embedded language implemented in a single .c file
afl, which is trivial to apply to this program:
-
TCL like interpreter suitable for embedded use
I made my own version of a TCL interpreter (well, a very TCL like langauge) derived from "picol" available at https://github.com/howerj/pickle. There are many different re-implementations and derivatives of this interpreter but they all seem very "crashy", this one has been significantly hardened by using a fuzzer on it which ran for months called American Fuzzy Lop https://lcamtuf.coredump.cx/afl/ . It is also more suitable for embedded use whilst still not having arbitrary restrictions like many other implementations.
-
What's in your tool belt?
On Linux afl is a very powerful bug-finding tool, and it's a great companion when doing code review. Composes well with ASan and UBSan.
- Afl - American fuzzy lop - a security-oriented fuzzer
-
Difficulty of CSCA48 compared to other first year cs/math courses
b-, https://lcamtuf.coredump.cx/afl/
What are some alternatives?
UNITS - a compile-time, header-only, dimensional analysis and unit conversion library built on c++14 with no dependencies.
boofuzz - A fork and successor of the Sulley Fuzzing Framework
stb - stb single-file public domain libraries for C/C++
honggfuzz - Security oriented software fuzzer. Supports evolutionary, feedback-driven fuzzing based on code coverage (SW and HW based)
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android
Cppcheck - static analysis of C/C++ code
libcpuid - a small C library for x86 CPU detection and feature extraction
HTTP Parser - http request/response parser for c
C++ Format - A modern formatting library
PHP CPP - Library to build PHP extensions with C++
libssh2 - the SSH library