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

New project: Qubes OS #637

Merged
merged 1 commit into from May 31, 2017

Conversation

Projects
None yet
3 participants
@jpouellet
Contributor

jpouellet commented May 31, 2017

Qubes OS wishes to improve its automated testing pipeline in various ways, one of which being the introduction of continuous fuzzing.

The initial work will be performed by @paraschetal as part of his Google Summer of Code project, for which I am the mentor.

There are many pieces of code in Qubes OS which could benefit from fuzzing, but initial focus is currently on the inter-vm file-copy unpacker, and the GUI protocol. (proto, impl)

According to https://github.com/google/oss-fuzz#accepting-new-projects, the way to request a new project be added to oss-fuzz is for a member of the project to submit a PR here. I'm not an official member of the Qubes OS team, but I am an active contributor. Hopefully that's good enough...

/cc @rootkovska @marmarek @paraschetal

New project: Qubes OS
Qubes OS wishes to improve its automated testing pipeline in various
ways, one of which being the introduction of continuous fuzzing.

The initial work will be performed by Paras Chetal as part of his
Google Summer of Code project [1], for which I am the mentor.

There are many pieces of code in Qubes OS which could benefit from
fuzzing, but initial focus is currently on the inter-vm file-copy
unpacker, and the GUI protocol [2][3].

According to [4], the way to request a new project be added to oss-fuzz
is for a member of the project to submit a PR here. I'm not an official
member of the Qubes OS team [5], but I am an active contributor.
Hopefully that's good enough...

[1]: https://summerofcode.withgoogle.com/projects/#5530206738579456
[2]: https://www.qubes-os.org/doc/gui/
[3]: https://github.com/QubesOS/qubes-gui-daemon/blob/master/gui-daemon/xside.c
[4]: https://github.com/google/oss-fuzz#accepting-new-projects
[5]: https://www.qubes-os.org/team/
@Dor1s

This comment has been minimized.

Collaborator

Dor1s commented May 31, 2017

Hi @jpouellet ,

Qubes OS seems to be an interesting project for the integration. We need a confirmation from the maintainers that they are OK with you and @paraschetal working on this :)

@marmarek

This comment has been minimized.

Contributor

marmarek commented May 31, 2017

We need a confirmation from the maintainers that they are OK with you and @paraschetal working on this :)

👍 from me

@Dor1s

This comment has been minimized.

Collaborator

Dor1s commented May 31, 2017

Thanks!

@Dor1s Dor1s merged commit b794dfe into google:master May 31, 2017

1 check passed

cla/google All necessary CLAs are signed

tmatth added a commit to tmatth/oss-fuzz that referenced this pull request Oct 22, 2018

[qubes-os] New project: Qubes OS (google#637)
Qubes OS wishes to improve its automated testing pipeline in various
ways, one of which being the introduction of continuous fuzzing.

The initial work will be performed by Paras Chetal as part of his
Google Summer of Code project [1], for which I am the mentor.

There are many pieces of code in Qubes OS which could benefit from
fuzzing, but initial focus is currently on the inter-vm file-copy
unpacker, and the GUI protocol [2][3].

According to [4], the way to request a new project be added to oss-fuzz
is for a member of the project to submit a PR here. I'm not an official
member of the Qubes OS team [5], but I am an active contributor.
Hopefully that's good enough...

[1]: https://summerofcode.withgoogle.com/projects/#5530206738579456
[2]: https://www.qubes-os.org/doc/gui/
[3]: https://github.com/QubesOS/qubes-gui-daemon/blob/master/gui-daemon/xside.c
[4]: https://github.com/google/oss-fuzz#accepting-new-projects
[5]: https://www.qubes-os.org/team/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment