app-forensics/aflplusplus
Fork of AFL, the popular compile-time instrumentation fuzzer
Screenshots
-
aflplusplus-5.03c~amd64 ~arm64 ~ppc64test +llvm_slot_22 llvm_slot_17 llvm_slot_18 llvm_slot_19 llvm_slot_20 llvm_slot_21 python_single_target_python3_12 python_single_target_python3_13 python_single_target_python3_14 python_single_target_python3_15
View 
Download 
Browse License: AGPL-3+ Apache-2.0 Overlay: bentoo -
aflplusplus-4.35c~amd64 ~arm64 ~ppc64test +llvm_slot_21 llvm_slot_16 llvm_slot_17 llvm_slot_18 llvm_slot_19 llvm_slot_20 python_single_target_python3_12 python_single_target_python3_13 python_single_target_python3_14
View Download Browse License: Apache-2.0 Overlay: gentoo
ChangeLog
commit 5b74685cfea35301324419ff26f6cac936f47c83
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Sep 11 21:16:47 2026 -0300
add(app-forensics/aflplusplus-5.03c, metadata/md5-cache/app-forensics/aflplusplus-5.03c), mod(.autoupdate/packages.toml)
Ported from ::gentoo, which stops at 4.35c, and carried across the 5.x
series boundary. New category in the overlay.
Two things stop this from being a copy of the ::gentoo ebuild:
* LICENSE. Upstream relicensed the project in 5.00c: the whole is now
AGPL-3.0-or-later, and only the files that could not be switched stay
Apache-2.0. ::gentoo still reads Apache-2.0 alone because it never left
4.x. Caught by reading the installed image -- afl-fuzz prints its own
license at startup, which the ebuild text does not.
* PATCHES. ::gentoo pulls three Gentoo patches as a 2nd SRC_URI from
dev.gentoo.org/~sam/. That tarball stops at 4.35c; 4.40c and every 5.x
version 404. The three are rebased onto 5.03c here and kept in files/,
so the package no longer depends on a distfile nobody regenerates.
Five hunks needed rebasing: upstream added $(COMPILER_RT_LDFLAGS) to the
runtime rules, reordered the SanitizerCoveragePCGUARD.so link flags, and
grew a qemu_bridge mode that the clean/distrib/binary-only targets now
recurse into.
LLVM_COMPAT widened to and PYTHON_COMPAT to python3_:
upstream declares LLVM_TOO_NEW_DEFAULT=23, so slot 22 is supported, and it
is what llvm-r2 selects by default here.
Verified locally, nothing merged (host has no sudo): pkgcheck --cache=no
clean; src_prepare applied all three patches; src_compile passed under
GCC 16.2 + LLVM 22 with -march=znver5 -O2 reaching the compiler, which is
what the respect-flags patch exists to prove; src_install produced a
working afl-fuzz and man pages free of the USE_ leak; gentoo-parity.sh
exits 0 with all five rows JUSTIFIED; check-openrc-coverage.sh PASS.
The autoupdate record probes releases/latest and states that a bump here
is not mechanical: the three patches touch files upstream edits every
release.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Sep 11 21:16:47 2026 -0300
add(app-forensics/aflplusplus-5.03c, metadata/md5-cache/app-forensics/aflplusplus-5.03c), mod(.autoupdate/packages.toml)
Ported from ::gentoo, which stops at 4.35c, and carried across the 5.x
series boundary. New category in the overlay.
Two things stop this from being a copy of the ::gentoo ebuild:
* LICENSE. Upstream relicensed the project in 5.00c: the whole is now
AGPL-3.0-or-later, and only the files that could not be switched stay
Apache-2.0. ::gentoo still reads Apache-2.0 alone because it never left
4.x. Caught by reading the installed image -- afl-fuzz prints its own
license at startup, which the ebuild text does not.
* PATCHES. ::gentoo pulls three Gentoo patches as a 2nd SRC_URI from
dev.gentoo.org/~sam/. That tarball stops at 4.35c; 4.40c and every 5.x
version 404. The three are rebased onto 5.03c here and kept in files/,
so the package no longer depends on a distfile nobody regenerates.
Five hunks needed rebasing: upstream added $(COMPILER_RT_LDFLAGS) to the
runtime rules, reordered the SanitizerCoveragePCGUARD.so link flags, and
grew a qemu_bridge mode that the clean/distrib/binary-only targets now
recurse into.
LLVM_COMPAT widened to and PYTHON_COMPAT to python3_:
upstream declares LLVM_TOO_NEW_DEFAULT=23, so slot 22 is supported, and it
is what llvm-r2 selects by default here.
Verified locally, nothing merged (host has no sudo): pkgcheck --cache=no
clean; src_prepare applied all three patches; src_compile passed under
GCC 16.2 + LLVM 22 with -march=znver5 -O2 reaching the compiler, which is
what the respect-flags patch exists to prove; src_install produced a
working afl-fuzz and man pages free of the USE_ leak; gentoo-parity.sh
exits 0 with all five rows JUSTIFIED; check-openrc-coverage.sh PASS.
The autoupdate record probes releases/latest and states that a bump here
is not mechanical: the three patches touch files upstream edits every
release.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>