Vind een bug in Google Chrome en ontvang 1000 euro

Google Chrome kan je rijk maken

Google is zeer serieus over haar eigen webbrowser. Mensen die een bug vinden in Google Chrome, kunnen vanaf nu aanspraak maken op forse vergoedingen, die kunnen oplopen tot 1000 euro. Voor de kleinste bug ontvang je nog altijd 350 euro. Dat maakte Google afgelopen week bekend. Doel is om Chrome volledig bugvrij te krijgen.

Op het Chromium weblog schrijft Google over de stap en de werkwijze: Any bug filed through the Chromium bug tracker (under the template “Security Bug") will qualify for consideration. As this is an experimental program, here are some guidelines in the form of questions and answers. Our base reward for eligible bugs is $500. If the panel finds a particular bug particularly severe or particularly clever, we envisage rewards of $1337. The panel may also decide a single report actually constitutes multiple bugs. As a consumer of the Chromium open source project, Google will be sponsoring the rewards.

Geinteresseerd? Lees dan ook even onderstaande voorwaarden.

Q) What bugs are eligible?
A) Any security bug may be considered. We will typically focus on High and Critical impact bugs, but any clever vulnerability at any severity might get a reward. Obviously, your bug won’t be eligible if you worked on the code or review in the area in question.

Q) How do I find out my bug was eligible?
A) You will see a provisional comment to that effect in the bug entry once we have triaged the bug.

Q) What if someone else also found the same bug?
A) Only the first report of a given issue that we were previously unaware of is eligible. In the event of a duplicate submission, the earliest filed bug report in the bug tracker is considered the first report.

Q) What about bugs present in Google Chrome but not the Chromium open source project?
A) Bugs in either build may be eligible. In addition, bugs in plugins that are part of the Chromium project and shipped with Google Chrome by default (e.g. Google Gears) may be eligible. Bugs in third-party plugins and extensions are ineligible.

Q) Will bugs disclosed publicly without giving Chromium developers an opportunity to fix them first still qualify?
A) We encourage responsible disclosure. Note that we believe responsible disclosure is a two-way street; it’s our job to fix serious bugs within a reasonable time frame.

Q) Do I still qualify if I disclose the problem publicly once fixed?
A) Yes, absolutely. We encourage open collaboration. We will also make sure to credit you in the relevant Google Chrome release notes and nominate you for the Google Security “thank you” section.

Q) What about bugs in channels other than Stable?
A) We are interested in bugs in the Stable, Beta and Dev channels. It’s best for everyone to find and fix bugs before they are released to the Stable channel.

Q) What about bugs in third-party components?
A) These bugs may be eligible (e.g. WebKit, libxml, image libraries, compression libraries, etc). Bugs will be ineligible if they are part of the base operating system as opposed to part of the Chromium source tree. In the event of bugs in a component shared with other software, we are happy to take care of responsibly notifying other affected parties.

Q) Who determines whether a given bug is eligible?
A) The panel includes Adam Barth, Chris Evans, Neel Mehta, SkyLined and Michal Zalewski.

Q) Can you keep my identity confidential from the rest of the world?
A) Yes. If selected as the recipient of a reward, and you accept, we will need your contact details in order to pay you. However — at your discretion, we can credit the bug to “anonymous” and leave the bug entry private.

Volg hyped.nl via:

Top vacatures

Volg hyped.nl via:

Online marketing blog

Reacties

@Nick, ouwe zeikerd .. Lijkt me een goed idee om je Engels wat bij te spijkeren

Johan, 6 februari 2010
Beetje knip en plak werk lijkt mij zo. Volgende keer misschien gewoon naar Nederlands vertalen?

Nick, 1 februari 2010