-
Notifications
You must be signed in to change notification settings - Fork 81
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Integrate cfg with libfuzzer testing
- split-input format: add trailing blob for config file The corpus needs some update. - __wrap_open extended to handle the configuration file. The configuration file, mutated by the fuzzer, is made available to the cfg.c implementation, analogously to the handling of authfile_fd. The conf_file_path variable will hold the expected file name. If the conf_file= option does not appear in the fuzzed argv, the conf_file_path variable is set with the CFG_DEFAULT_PATH. conf_file_path might also be NULL if the test does not involve the use of a configuration file: this happens in the fuzz_format_parsers case.
- Loading branch information
Showing
5 changed files
with
101 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,3 +5,5 @@ set_authfile | |
set_conv | ||
set_user | ||
set_wiredata | ||
set_conf_file_fd | ||
set_conf_file_path |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters