hsivonen / hsivonen/encoding_rs

Integration with oss-fuzz fuzzing service

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
464
Forks
70
Avg merge
2d 4h
Merged PRs (30d)
2

Description

Hi @hsivonen, I would like to help integrate this project into OSS-Fuzz.

  • As an initial step for integration I have created this PR: https://github.com/google/oss-fuzz/pull/8652, it contains necessary logic from an OSS-Fuzz perspective to integrate encoding_rs.

  • OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects.

  • As encoding_rs already have cargo-fuzz based fuzzing implemented, this makes it easily compatible with oss-fuzz out of box.

  • If you would like to integrate, the only thing I need is a list of email(s), it must be associated with a google account like
    gmail (why?). by doing that, the provided email(s) will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats.

  • As an alternative, if you don't have a google/gmail id, but still wish to integrate. I can add my mail id for time being and monitor bug/crashes.

  • Notice the email(s) affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the OSS-Fuzz integration PR 8652 and the project's existing cargo-fuzz setup. The integration is done when OSS-Fuzz accepts the project configuration and the maintainer provides the required public Google-account email addresses.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.