Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port oss-fuzz fuzzers to Mbed TLS 3.0 #4790

Closed
4 tasks done
gilles-peskine-arm opened this issue Jul 19, 2021 · 3 comments
Closed
4 tasks done

Port oss-fuzz fuzzers to Mbed TLS 3.0 #4790

gilles-peskine-arm opened this issue Jul 19, 2021 · 3 comments
Assignees
Labels
enhancement needs-review Every commit must be reviewed by at least two team members, needs-reviewer This PR needs someone to pick it up for review size-m Estimated task size: medium (~1w)

Comments

@gilles-peskine-arm
Copy link
Contributor

gilles-peskine-arm commented Jul 19, 2021

The goal of this task is to switch the oss-fuzz fuzzers to Mbed TLS 3.0, reverting google/oss-fuzz#5636.

Goal of this task:

I have done a preliminary investigation and if I haven't missed anything, the only necessary change is to make some mbedtls_ecp_curve_info fields accessible to ecfuzzer, with no changes needed to any of the fuzzer projects.

This should be done at the latest before 2.2x becomes LTS, since the fuzzers should run on the latest code with all the features.

@gilles-peskine-arm gilles-peskine-arm added enhancement size-m Estimated task size: medium (~1w) labels Jul 19, 2021
@gilles-peskine-arm gilles-peskine-arm self-assigned this Jul 19, 2021
@bensze01 bensze01 modified the milestone: 2.x pre-LTS work Jul 28, 2021
@bensze01 bensze01 removed this from the 2.x pre-LTS work milestone Aug 11, 2021
@daverodgman
Copy link
Contributor

3/4 projects on OSS-fuzz have been updated; only cryptofuzz remains. There is an open PR for this:

google/oss-fuzz#6992 but this does depend on crypto-fuzz making some updates first.

@daverodgman
Copy link
Contributor

crypto-fuzz is now updated, so oss-fuzz is fully fuzzing against the development branch. I think we can close this now.

@daverodgman daverodgman added needs-review Every commit must be reviewed by at least two team members, needs-reviewer This PR needs someone to pick it up for review labels Jan 28, 2022
@paul-elliott-arm
Copy link
Member

Closing this as it appears to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement needs-review Every commit must be reviewed by at least two team members, needs-reviewer This PR needs someone to pick it up for review size-m Estimated task size: medium (~1w)
Projects
None yet
Development

No branches or pull requests

4 participants