Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: fuzzing anybody
Date: Tue, 6 Dec 2016 13:26:09 +0100	[thread overview]
Message-ID: <201612061326.09245.sweet_f_a@gmx.de> (raw)

Hello,

google is offereing "Fuzz testing" for famous OSS projects
  https://github.com/google/oss-fuzz

I've thought this might be a nice idea for util-linux and already 
registered
  https://github.com/google/oss-fuzz/pull/120

Stupidly I've missed the point that I would also need to write some code 
which intelligently feeds our UL programs with the generated random 
data to find bugs. I thought that this is what google would do for us 
but they only give us the their infrastructure for running the actual 
tests. ;)

So if anybody is interested in this fuzzing topic ... maybe someone has 
a good idea, say how to feed libsmartcol or libblkid with random data.

A good and even interesting point to start is this "libFuzzer Tutorial":
https://github.com/google/fuzzer-test-suite/blob/master/tutorial/libFuzzerTutorial.md

Also interesting to see how other projects are doing it already in 
google's oss-fuzz.

for example curl: 
https://github.com/google/oss-fuzz/blob/master/projects/curl/curl_fuzzer.cc

or openssl which has a fuzz/ sub-directory in their original project.
https://github.com/openssl/openssl/tree/master/fuzz

cu,
Rudi

             reply	other threads:[~2016-12-06 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 12:26 Ruediger Meier [this message]
2016-12-06 14:31 ` fuzzing anybody Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201612061326.09245.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox