openssl / openssl/fuzz-corpora

Should we have some github action checks in this repository?

Open
#4 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
6
Forks
22
PR merge metrics
No merged PRs in 30d

Description

This follows #3. To be able to fix bugs discovered by new before it hits openssl/openssl, a test build + run should be made in PRs done here. I really can't imagine it being very hard, if you consider running the related OpenSSL test recipes with a corpora that's not in the OpenSSL source tree. This patch in OpenSSL should help:

diff --git a/test/recipes/fuzz.pl b/test/recipes/fuzz.pl
index 3f03eef4f7..549970d137 100644
--- a/test/recipes/fuzz.pl
+++ b/test/recipes/fuzz.pl
@@ -8,6 +8,7 @@
 use strict;
 use warnings;
 
+use File::Spec;
 use OpenSSL::Glob;
 use OpenSSL::Test qw/:DEFAULT srctop_dir/;
 
@@ -15,7 +16,8 @@ sub fuzz_ok {
     die "Only one argument accepted" if scalar @_ != 1;
 
     my $f = $_[0];
-    my $d = srctop_dir('fuzz', 'corpora', $f);
+    my $d = ENV{FUZZ_CORPORA} // srctop_dir('fuzz', 'corpora');
+    $d = File::Spec->catdir($d, $f);
 
     SKIP: {
         skip "No directory $d", 1 unless -d $d;

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the related OpenSSL test recipes and the proposed change in test/recipes/fuzz.pl, including the FUZZ_CORPORA path. Determine how a PR check can build and run those recipes against this repository’s corpora; done means the check runs automatically for pull requests and reports failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.