Rezultati pretraživanja
  1. 26. kol 2019.

    Ok, rewind to early 2017. My team was going to write a SPIR-V backend to DXC, lovingly called Spiregg . Question was: how were we going to test it?

    Prikaži ovu nit
  2. 11. svi 2018.

    GDAL 2.3.0 released! Sadly, I didn't get to test the release candidates (newborn human in the house) has been crazy productive and this... "More than 1000 fixes for issues/vulnerabilities found by OSS-Fuzz"

  3. 14. tra 2018.

    Woo, the 1000th bug against has just been filed ! (actually a bit less since a few ones were actually in other dependant libraries). 977 of them have been fixed. Most remaining ones are unreproducible

  4. 14. srp 2019.

    Fuzz Driver Generation at Scale! Check out the preprint of our paper at: work w/ D. Babic, , Y. Chen, , T. King, M. Kusano, , W. Wang. See you at in August!

  5. 30. kol 2019.

    I am really proud of my team for receiving a best paper award at ! Check it out at . We synthesize drivers that find security and reliability issues using fuzzing. Many run in - supported with integration rewards

  6. Finally got integrated into 🤘 and interesting bugs from 2003 code are popping up :)

  7. 17. pro 2017.

    has so far been > 14% of the bugs. Measured by 675 commits crediting OSS Fuzz and OSS Fuzz being at about bug 4672. Credit to for bug fixing!

  8. 6. tra 2018.

    creativity makes me discover features of GDAL I was unaware of. For example "ogr2ogr myoutputdatasource myinputdatasourcewithseverallayers -nln somename" will 'merge' all the input layers into a single one (for drivers that support adding fields to non empty layers)

  9. 30. ožu 2018.

    Ironically the fuzzer for ogr2ogr I wrote to find bugs in the writing part of drivers also helps finding bugs in the reading part :-)

  10. 23. svi 2019.

    Sharing bounty with ... Help would now be appreciated for merging it with latest

  11. 7. sij 2018.

    As of last week is integrated with public . Already found and fixed multiple bugs. Thanks Daniel Salzman and (and ) for your support and prompt attention! /cc .

  12. 24. lip 2019.

    Who analyses an OSS project’s security over time? Check out these 4 open security examples that are raising the bar -

  13. 12. kol 2019.

    is now fuzzing GDAL on i386 and has already found a few 32-bit specific (or generic but easier to spot) bugs

  14. 27. lip 2017.

    I'm crediting in ticket commits for bugs it discovered in ... fuzzers I wrote for it...

  15. oss-fuzz integration has been merged into {fmt}: Thanks to !

  16. 21. svi 2017.

    In 11 days of use of on , we have pushed 151 related commits in trunk. Impressive technology ! Hope things will calm down now

  17. 9. lip 2017.

    Crazy that this UK/Ordnance Survey NTF vector format, that no one no longer uses, generates so many bug reports.

  18. Thanks to {fmt} now has a shiny new oss-fuzz badge and the first short-lived regression found by fuzzer has been fixed!

  19. 19. lis 2019.

    Discovering from Bas email that someone has taken care of registering a CVE at least for one of the GDAL issues: . Why this one and not others is a mystery :-)

  20. 22. tra 2017.

    Proposed inclusion in . Hoping for the best.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.