Note that OSS-Fuzz only supports C/C++ libs. Not Python Fuzzed binaries must statically link all their dependencies: https://github.com/google/oss-fuzz/blob/master/docs/fuzzer_environment.md
Even > Hi, > > here an idea for https://trac.osgeo.org/grass/wiki/GSoC/2019 > > Since I am not the right person to follow a student on this, I put it here: > > === Continuous Fuzzing for GRASS GIS to uncover software bugs === > > * TL;DR: Fuzz testing is a well-known technique for uncovering > various kinds of programming errors in software. Many of these > detectable errors (e.g. buffer overflow) can have serious security > implications. The student will make GRASS GIS ready for OSS-Fuzz. > * https://github.com/google/oss-fuzz OSS-Fuzz - Continuous Fuzzing > for Open Source Software > * Requirements: > * Student needs to show understanding of the GRASS GIS software > structure and significantly extend on text above in the proposal. > * Language: Python, C > * Mentors: ... > * Co-mentors: ... > * Proposed by: ... > > Here the full template to be used: > https://lists.osgeo.org/pipermail/discuss/2019-February/038233.html > > Maybe someone here would like to take over to write up the idea properly? > > Markus > _______________________________________________ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev