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

Google account requirement for project enrolment #1915

Closed
bshastry opened this issue Oct 31, 2018 · 3 comments
Closed

Google account requirement for project enrolment #1915

bshastry opened this issue Oct 31, 2018 · 3 comments

Comments

@bshastry
Copy link
Contributor

bshastry commented Oct 31, 2018

Hello,

It is clear from the documentation that a Google account is needed to enrol a project into oss-fuzz.

Our ClusterFuzz fuzzing infrastructure and issue tracker require a Google account for authentication. Note that an alternate email address associated with a Google acount does not work due to appengine api limitations.

The xz (#402 and #1892 #1287 ) project is almost ready to be added to oss-fuzz but its maintainer does not intend on creating a Google account. So, is Google's position in this situation wontfix i.e., no alternate arrangements possible?

P.S. It seems xz is being fuzzed built as a dependency of the imagemagick fuzzer

Thanks

@oliverchang
Copy link
Collaborator

If the maintainer does not have a Google account, they will not be able to access most of our dashboards, including access to crash reports and reproducers. If listed in our projet.yaml, they will be still be able to receive email updates on our bug tracker, but may not be able to comment in issues.

In this case I think the only solution is to find some acceptable intermediary who does have a Google account and can forward the testcases and whatever else is required to the maintainer.

@bshastry
Copy link
Contributor Author

If the maintainer does not have a Google account, they will not be able to access most of our dashboards, including access to crash reports and reproducers. If listed in our projet.yaml, they will be still be able to receive email updates on our bug tracker, but may not be able to comment in issues.

In this case I think the only solution is to find some acceptable intermediary who does have a Google account and can forward the testcases and whatever else is required to the maintainer.

Thank you @oliverchang . iiuc, inclusion of a non-Google account in project.yaml permits

  • viewing bug reports

does not permit

  • access to crash reports, test cases etc

I will discuss this with the maintainer.

@jonathanmetzman
Copy link
Contributor

Duplicate: #2261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants