You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by vy...@apache.org on 2024/09/04 11:54:01 UTC
(logging-log4j2) branch fuzzing updated: Fix typo
This is an automated email from the ASF dual-hosted git repository.
vy pushed a commit to branch fuzzing
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/fuzzing by this push:
new 0300b3aacb Fix typo
0300b3aacb is described below
commit 0300b3aacb6797ee8da2f4297aadaa6923304e6a
Author: Volkan Yazıcı <vo...@yazi.ci>
AuthorDate: Wed Sep 4 13:54:22 2024 +0200
Fix typo
---
FUZZING.adoc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/FUZZING.adoc b/FUZZING.adoc
index 6ceb826995..838a89419a 100644
--- a/FUZZING.adoc
+++ b/FUZZING.adoc
@@ -95,11 +95,12 @@ Access to both the web interface and the bucket is restricted, and only allowed
[#reproduce]
=== How can I reproduce fuzzing failures detected by OSS-Fuzz?
-Download the associated `.testcase` file from the https://console.cloud.google.com/storage/browser/log4j2-logs.clusterfuzz-external.appspot.com[the Google Cloud Storage bucket], and run the following command:
+Download the associated `.testcase` file from https://console.cloud.google.com/storage/browser/log4j2-logs.clusterfuzz-external.appspot.com[the Google Cloud Storage bucket], and run the following command:
[source,bash]
----
-python infra/helper.py reproduce log4j2 <FUZZ-TARGET-NAME> <TESTCASE-FILE-PATH>
+python infra/helper.py reproduce \
+ log4j2 <FUZZ-TARGET-NAME> <TESTCASE-FILE-PATH>
----
Refer to https://google.github.io/oss-fuzz/advanced-topics/reproducing/[the related OSS-Fuzz documentation] for details.