pcp
[Top] [All Lists]

Re: Checking PCP archives - RFC

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: Checking PCP archives - RFC
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 23 May 2013 06:34:43 +1000
Cc: PCP Mailing List <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20130522132819.GJ28935@xxxxxxxxxx>
References: <519AC94B.9020904@xxxxxxxxxxxxxxxx> <y0mfvxgl3r3.fsf@xxxxxxxx> <519C0AA9.5010706@xxxxxxxxxxxxxxxx> <20130522132819.GJ28935@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
On 22/05/13 23:28, Frank Ch. Eigler wrote:
...
(Yes, fuzzing can include structured data, by teaching it the grammar of
PCP archives but then messing with the productions randomly.)

Frank do you have a pointer to an available toolkit that would be suitable for this sort of effort? I've read about, but never used fuzzers. In the PCP QA suite, the src/mkbadlen script demonstrates the sort of deterministic approach I have used and was planning to extend to create corrupted archives.

Sure (though till corruption repair comes online, this could be a few-liner
program that just uses the hypothetical PM_CTXFLAG_LINT flag).

Or the pmNewContext support for the hypothetical PM_CTXFLAG_LINT flag could be a system() call ... 8^)> ... at this point I am not expecting any of the pmlogcheck code to end up in libpcp (or any other library).

<Prev in Thread] Current Thread [Next in Thread>