diff --git a/fuzzers/baby/baby_fuzzer_swap_differential/README.md b/fuzzers/baby/baby_fuzzer_swap_differential/README.md index b16ab4611e..211ea10a52 100644 --- a/fuzzers/baby/baby_fuzzer_swap_differential/README.md +++ b/fuzzers/baby/baby_fuzzer_swap_differential/README.md @@ -7,5 +7,5 @@ It runs on a single core until an input is discovered which both inputs accept. The tested programs are provided in `first.c` and `second.c`. -You may execute this fuzzer with `cargo make run`. If you prefer to do so manually, you may also simply use +You may execute this fuzzer with `just run`. If you prefer to do so manually, you may also simply use `cargo build --release --bin libafl_cc` followed by `cargo run --release --bin fuzzer_sd` \ No newline at end of file diff --git a/fuzzers/binary_only/frida_executable_libpng/README.md b/fuzzers/binary_only/frida_executable_libpng/README.md index 54c45ddd1a..cd2dd52d06 100644 --- a/fuzzers/binary_only/frida_executable_libpng/README.md +++ b/fuzzers/binary_only/frida_executable_libpng/README.md @@ -12,7 +12,7 @@ Then, it will build (the C++ harness)[./harness.cc] and the instrumented `libpng Then, it will create frida fuzzer shared library in `./target/release/libfrida_fuzzer.so`. On unix platforms, you'll need [libc++](https://libcxx.llvm.org/) to build it. -Alternatively you can run `cargo make run` and this command will automatically build and run the fuzzer +Alternatively you can run `just run` and this command will automatically build and run the fuzzer ### Build For Android When building for android using a cross-compiler, make sure you have a [_standalone toolchain_](https://developer.android.com/ndk/guides/other_build_systems), and then add the following: diff --git a/fuzzers/binary_only/frida_libpng/README.md b/fuzzers/binary_only/frida_libpng/README.md index 648a702296..f2f6234df9 100644 --- a/fuzzers/binary_only/frida_libpng/README.md +++ b/fuzzers/binary_only/frida_libpng/README.md @@ -12,7 +12,7 @@ Then, it will link (the fuzzer)[./src/fuzzer.rs] against (the C++ harness)[./har Afterwards, the fuzzer will be ready to run, from `target/frida_libpng`. On unix platforms, you'll need [libc++](https://libcxx.llvm.org/) to build it. -Alternatively you can run `cargo make run` and this command will automatically build and run the fuzzer +Alternatively you can run `just run` and this command will automatically build and run the fuzzer ### Build For Android When building for android using a cross-compiler, make sure you have a [_standalone toolchain_](https://developer.android.com/ndk/guides/other_build_systems), and then add the following: diff --git a/fuzzers/binary_only/intel_pt_baby_fuzzer/README.md b/fuzzers/binary_only/intel_pt_baby_fuzzer/README.md index 2ca0054b3a..92fd87613d 100644 --- a/fuzzers/binary_only/intel_pt_baby_fuzzer/README.md +++ b/fuzzers/binary_only/intel_pt_baby_fuzzer/README.md @@ -12,6 +12,6 @@ After building this example with `cargo build`, you need to give to the executab You can run this example using `cargo run`, and you can enable the TUI feature by building and running with `--features tui`. -As an alternative, simply run `cargo make` to build and run the fuzzer (requires `cargo-make`). +As an alternative, simply run `just` to build and run the fuzzer (requires `just`). This fuzzer is compatible with Linux hosts only having an Intel PT compatible CPU. diff --git a/fuzzers/binary_only/intel_pt_command_executor/README.md b/fuzzers/binary_only/intel_pt_command_executor/README.md index 967733b505..255823f9b0 100644 --- a/fuzzers/binary_only/intel_pt_command_executor/README.md +++ b/fuzzers/binary_only/intel_pt_command_executor/README.md @@ -6,14 +6,14 @@ Processor Trace (PT) to compute code coverage. ## Prerequisites - A Linux host with an Intel Processor Trace (PT) compatible CPU -- `cargo-make` installed +- `just` installed - Sudo access to grant necessary capabilities to the fuzzer ## How to Run the Fuzzer To compile and run the fuzzer (and the target program) execute the following command: ```sh -cargo make +just ``` > **Note**: This command may prompt you for your password to assign capabilities required for Intel PT. If you'd prefer diff --git a/fuzzers/binary_only/qemu_cmin/README.md b/fuzzers/binary_only/qemu_cmin/README.md index 9b22b87e98..6b859f5536 100644 --- a/fuzzers/binary_only/qemu_cmin/README.md +++ b/fuzzers/binary_only/qemu_cmin/README.md @@ -30,9 +30,9 @@ sudo apt install \ Defaults to `x86_64` architecture ```bash -cargo make run +just run ``` ```bash -cargo make +just ``` diff --git a/fuzzers/binary_only/qemu_coverage/README.md b/fuzzers/binary_only/qemu_coverage/README.md index 322ffe126a..eb91c67e2a 100644 --- a/fuzzers/binary_only/qemu_coverage/README.md +++ b/fuzzers/binary_only/qemu_coverage/README.md @@ -31,9 +31,9 @@ sudo apt install \ Defaults to `x86_64` architecture ```bash -cargo make run +just run ``` ```bash -cargo make +just ``` diff --git a/fuzzers/binary_only/qemu_launcher/README.md b/fuzzers/binary_only/qemu_launcher/README.md index 3b7d3dfea7..96080bd494 100644 --- a/fuzzers/binary_only/qemu_launcher/README.md +++ b/fuzzers/binary_only/qemu_launcher/README.md @@ -39,9 +39,9 @@ sudo apt install \ Defaults to `x86_64` architecture. Change the architecture by ```bash -cargo make run +just run ``` ```bash -cargo make +just ``` diff --git a/fuzzers/binary_only/tinyinst_simple/README.md b/fuzzers/binary_only/tinyinst_simple/README.md index 9d507df6c2..439edaf1ed 100644 --- a/fuzzers/binary_only/tinyinst_simple/README.md +++ b/fuzzers/binary_only/tinyinst_simple/README.md @@ -6,7 +6,7 @@ This is a fuzzer example to show how libafl_tinyinst works. 2. Build the harness with `cl test\test.cpp -o test.exe` 3. Build the fuzzer with `cargo build --release`. The fuzzer is `target\release\tinyinst_simple.exe` -## Run with cargo-make -Or, you can simply run it using cargo-make +## Run with just +Or, you can simply run it using just 1. If on Windows, open up a developer powershell so that you have access to cl (Windows Default Compiler) -2. Run `cargo make run` to run the fuzzer +2. Run `just run` to run the fuzzer diff --git a/fuzzers/forkserver/forkserver_libafl_cc/README.md b/fuzzers/forkserver/forkserver_libafl_cc/README.md index a3a93e5041..496db40f69 100644 --- a/fuzzers/forkserver/forkserver_libafl_cc/README.md +++ b/fuzzers/forkserver/forkserver_libafl_cc/README.md @@ -4,10 +4,10 @@ This is a simple example fuzzer to fuzz an executable instrumented by libafl_cc. ## Usage -You can build this example by running `cargo make fuzzer`. +You can build this example by running `just fuzzer`. This compiles, libafl_cc, the fuzzer and the example harness program in `src/program.c` with libafl_cc. ## Run -You can run this example by running `cargo make run`. +You can run this example by running `just run`. diff --git a/fuzzers/full_system/nyx_libxml2_parallel/README.md b/fuzzers/full_system/nyx_libxml2_parallel/README.md index 5a7bdc49a3..87658d612f 100644 --- a/fuzzers/full_system/nyx_libxml2_parallel/README.md +++ b/fuzzers/full_system/nyx_libxml2_parallel/README.md @@ -12,4 +12,4 @@ the following command will: ``` # run the fuzzer -use `cargo make run` to run the fuzzer. If you have setup all environment, you can use `cargo run` directly. +use `just run` to run the fuzzer. If you have setup all environment, you can use `cargo run` directly. diff --git a/fuzzers/full_system/nyx_libxml2_standalone/README.md b/fuzzers/full_system/nyx_libxml2_standalone/README.md index 5a7bdc49a3..87658d612f 100644 --- a/fuzzers/full_system/nyx_libxml2_standalone/README.md +++ b/fuzzers/full_system/nyx_libxml2_standalone/README.md @@ -12,4 +12,4 @@ the following command will: ``` # run the fuzzer -use `cargo make run` to run the fuzzer. If you have setup all environment, you can use `cargo run` directly. +use `just run` to run the fuzzer. If you have setup all environment, you can use `cargo run` directly. diff --git a/fuzzers/full_system/qemu_linux_kernel/README.md b/fuzzers/full_system/qemu_linux_kernel/README.md index 528a3d4414..eccf39561f 100644 --- a/fuzzers/full_system/qemu_linux_kernel/README.md +++ b/fuzzers/full_system/qemu_linux_kernel/README.md @@ -16,24 +16,24 @@ TODO To build the target: ```bash -cargo make target +just target ``` To build the fuzzer: ```bash -cargo make build +just build ``` It is also possible to update the target if it only changes "runtime" files. This is equivalent to rebuilding the target, it is only faster since it does not need to rebuild the image from scratch. Check [The linux builder repository](https://github.com/AFLplusplus/linux-qemu-image-builder.git) for more details on the specifics. ```bash -cargo make target_update +just target_update ``` ## Run To run the fuzzer: ```bash -cargo make run +just run ``` \ No newline at end of file diff --git a/fuzzers/full_system/qemu_linux_process/README.md b/fuzzers/full_system/qemu_linux_process/README.md index 08c9f01e82..53408b06bd 100644 --- a/fuzzers/full_system/qemu_linux_process/README.md +++ b/fuzzers/full_system/qemu_linux_process/README.md @@ -17,24 +17,24 @@ TODO To build the target: ```bash -cargo make target +just target ``` To build the fuzzer: ```bash -cargo make build +just build ``` It is also possible to update the target if it only changes "runtime" files. This is equivalent to rebuilding the target, it is only faster since it does not need to rebuild the image from scratch. Check [The linux builder repository](https://github.com/AFLplusplus/linux-qemu-image-builder.git) for more details on the specifics. ```bash -cargo make target_update +just target_update ``` ## Run To run the fuzzer: ```bash -cargo make run +just run ``` \ No newline at end of file diff --git a/fuzzers/fuzz_anything/baby_fuzzer_wasm/README.md b/fuzzers/fuzz_anything/baby_fuzzer_wasm/README.md index 52080e68dd..03316b4521 100644 --- a/fuzzers/fuzz_anything/baby_fuzzer_wasm/README.md +++ b/fuzzers/fuzz_anything/baby_fuzzer_wasm/README.md @@ -3,7 +3,7 @@ A brief demo demonstrating libafl's compatibility with WASM, and how to do it. In this example, the entire LibAFL harness and target are present in a WASM binary, which is then loaded by [the example -webpage](pkg/index.html). To run this example, do `cargo make build`, then open [the example webpage](pkg/index.html) in +webpage](pkg/index.html). To run this example, do `just build`, then open [the example webpage](pkg/index.html) in your browser (via something like `python3 -m http.server`). The fuzzer will execute until finding a solution and will write the fuzzer log to your console. diff --git a/fuzzers/inprocess/libfuzzer_windows_asan/README.md b/fuzzers/inprocess/libfuzzer_windows_asan/README.md index 357510c8d5..3ac7adbb17 100644 --- a/fuzzers/inprocess/libfuzzer_windows_asan/README.md +++ b/fuzzers/inprocess/libfuzzer_windows_asan/README.md @@ -29,7 +29,7 @@ After that clang should be available in the PATH. To build the fuzzer and link against the `harness.cpp` in this example run: ``` -cargo make fuzzer +just fuzzer ``` ## Running diff --git a/utils/gdb_qemu/README.md b/utils/gdb_qemu/README.md index d391f3fe4d..f36ccfc6a3 100644 --- a/utils/gdb_qemu/README.md +++ b/utils/gdb_qemu/README.md @@ -4,7 +4,7 @@ # Test ``` rustup target add powerpc-unknown-linux-gnu -$ cargo make gdb +$ just gdb ``` # Example diff --git a/utils/noaslr/README.md b/utils/noaslr/README.md index 739631b888..2a7925aec5 100644 --- a/utils/noaslr/README.md +++ b/utils/noaslr/README.md @@ -13,12 +13,12 @@ time it is run. # Test ## App ``` -$ cargo make run +$ just run ``` ## Library ``` -$ cargo make runlib +$ just runlib ``` # Example