Hi everybody,
the Qt project is now registered in oss-fuzz's list of projects:
https://github.com/google/oss-fuzz/tree/master/projects
What I have so far:
- fuzzing Qt with libFuzzer locally
- registered Qt project for oss-fuzz
What I don't have so far:
- setting up build/run on Google's server
Hello Robert,
On 05.09.2018 13:08, Robert Löhning wrote:
> if (x == 0)
> foo()
> else
> bar()
>
> Then all values of x will be considered different. For fuzzing, though,
> only the two cases x == 0 and x != 0 will matter.
>
> Do I miss something here?
yes I think it would consider all com
Am 05.09.2018 um 12:40 schrieb Peter Hartmann:
> Hello Robert,
>
> On 04.09.2018 14:03, Robert Löhning wrote:
>> I saw your post and it helped me get started. Thanks for that!
>
> cool, thanks for the feedback!
>
>>
>> By the way: In step 1 you use
>> -fsanitize-coverage=edge
>> whereas I follow
Hello Robert,
On 04.09.2018 14:03, Robert Löhning wrote:
> I saw your post and it helped me get started. Thanks for that!
cool, thanks for the feedback!
>
> By the way: In step 1 you use
> -fsanitize-coverage=edge
> whereas I followed LLVM's example [1] and used
> -fsanitize-coverage=trace-pc-gu
Hi Peter,
I saw your post and it helped me get started. Thanks for that!
By the way: In step 1 you use
-fsanitize-coverage=edge
whereas I followed LLVM's example [1] and used
-fsanitize-coverage=trace-pc-guard
Unfortunately the documentation seems to be a bit scarce. Could you
please tell me b
Peter Hartmann (4 September 2018 11:17)
> sounds like a good initiative, I was asking about the same thing 2
> years ago ([1]) but then somehow didn't follow up on this.
>
> Back then I also wrote some simple fuzzing test cases ([2]) that found
> some crashes and memory corruptions ([3]), I would b
Hello,
sounds like a good initiative, I was asking about the same thing 2 years
ago ([1]) but then somehow didn't follow up on this.
Back then I also wrote some simple fuzzing test cases ([2]) that found
some crashes and memory corruptions ([3]), I would be happy to
contribute them if they are de
El divendres, 31 d’agost de 2018, a les 11:24:58 CEST, Robert Löhning va
escriure:
> Hi everybody,
>
> yes I did. So far I have been working on getting Qt into a better shape
> for fuzzing at all, resulting in [1].
>
> This prepares a Qt build for being fuzz tested with clang's libFuzzer,
> the
El divendres, 31 d’agost de 2018, a les 11:31:16 CEST, Robert Löhning va
escriure:
> Am 30.08.2018 um 21:30 schrieb Albert Astals Cid via Development:
> > El dijous, 30 d’agost de 2018, a les 8:59:40 CEST, André Pönitz va
escriure:
> >> On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid
Am 30.08.2018 um 21:30 schrieb Albert Astals Cid via Development:
El dijous, 30 d’agost de 2018, a les 8:59:40 CEST, André Pönitz va escriure:
On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid via
Development wrote:
I made a local test run of the undefined sanitizer and it found
http
Hi everybody,
yes I did. So far I have been working on getting Qt into a better shape
for fuzzing at all, resulting in [1].
This prepares a Qt build for being fuzz tested with clang's libFuzzer,
the tool that Google also uses in oss-fuzz. The fuzzer I used for
testing my setup already found
El divendres, 31 d’agost de 2018, a les 10:27:08 CEST, Edward Welbourne va
escriure:
>> By "fixed" do they mean "we have told them we've fixed it" or "we've
>> released all currently releasing branches of Qt with fixes" ?
Albert Astals Cid (31 August 2018 10:52)
> Fixed means "the daily bot has r
El divendres, 31 d’agost de 2018, a les 10:27:08 CEST, Edward Welbourne va
escriure:
> Albert Astals Cid (30 August 2018 20:42) wrote:
> > oss-fuzz is an online fuzzing service run by Google.
>
> Sounds useful.
>
> > They test daily the code base and run fuzzying over it, maintaining a
> > list
Albert Astals Cid (30 August 2018 20:42) wrote:
> oss-fuzz is an online fuzzing service run by Google.
Sounds useful.
> They test daily the code base and run fuzzying over it, maintaining a
> list of open and closed bugs.
>
> Found bugs are sent to a list of trusted address and kept private for
>
El dijous, 30 d’agost de 2018, a les 20:42:11 CEST, Albert Astals Cid via
Development va escriure:
> Unfortunately I have not been able to compile with the memory sanitizer
> enabled yet.
Done :)
https://github.com/albert-astals-cid-kdab/oss-fuzz/commit/b4f28e7dc5e4b936166cda1be36c3bde6b62c53d
El dijous, 30 d’agost de 2018, a les 8:59:40 CEST, André Pönitz va escriure:
> On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid via
>
> Development wrote:
> > I made a local test run of the undefined sanitizer and it found
> > https://paste.kde.org/prkox41mx in a few seconds, so "it wor
Hi Albert,
Nice! Robert has been working on exactly the same thing lately. I think it
would be good if you guys coordinated the effort :)
It would be ideal, if we could somehow get those mails forwarded to the
security mailing list. I wonder whether we could do that with a special mail
account
On Thu, Aug 30, 2018 at 08:42:11PM +0200, Albert Astals Cid via
Development wrote:
> I made a local test run of the undefined sanitizer and it found
> https://paste.kde.org/prkox41mx in a few seconds, so "it works"
>
> If you want to test it locally you can do python infra/helper.py
> build_fuzzer
oss-fuzz is an online fuzzing service run by Google.
They test daily the code base and run fuzzying over it, maintaining a list of
open and closed bugs.
As example you can see one of the poppler issues i fixed at
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9382
Everything is don
19 matches
Mail list logo
