Skip to content

Add Github Action: OneFuzz #7638

@WSLUser

Description

@WSLUser

Description of the new feature/enhancement

https://www.microsoft.com/security/blog/2020/09/15/microsoft-onefuzz-framework-open-source-developer-tool-fix-bugs/

What was once attached—at great expense—can now be baked into continuous build systems through:

Crash detection, once attached via tools such as Electric Fence, can be baked in with asan.
Coverage tracking, once attached via tools such as iDNA, Dynamo Rio, and Pin can be baked in with sancov.
Input harnessing, once accomplished via custom I/O harnesses, can be baked in with libfuzzer’s LLVMFuzzerTestOneInput function prototype.

Proposed technical implementation details (optional)

It's already being used internally by Windows. As this is a MS project, this should be able to be easily adopted. Source code will be published at https://github.com/microsoft/onefuzz during CppCon 2020.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Needs-Tag-FixDoesn't match tag requirementsNeeds-TriageIt's a new issue that the core contributor team needs to triage at the next triage meetingTracking-ExternalThis bug isn't resolved, but it's following an external workitem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions