contest-faq.html revision 5f1c94371a64b3196d4be9466099bb892df9b88e
1{{+bindTo:partials.standard_nacl_article}} 2 3<section id="security-contest-faq"> 4<span id="contest-faq"></span><h1 id="security-contest-faq"><span id="contest-faq"></span>Security Contest FAQ</h1> 5<aside class="caution"> 6The Native Client Security Contest has ended—check out the 7<a class="reference internal" href="/native-client/community/security-contest/index.html#contest-winners"><em>winning submissions</em></a>. We welcome your 8continued involvement in the project. You can help by submitting 9<a class="reference external" href="http://code.google.com/p/nativeclient/issues/list">bugs</a> and 10participating in the <a class="reference external" href="http://groups.google.com/group/native-client-discuss">Native Client discussion group</a>. 11</aside> 12<p>This FAQ is provided for reference only. For the complete official 13contest rules, see the Terms and Conditions.</p> 14<div class="contents local" id="contents" style="display: none"> 15<ul class="small-gap"> 16<li><a class="reference internal" href="#what-is-this-contest-about" id="id1">What is this contest about?</a></li> 17<li><a class="reference internal" href="#where-can-i-get-more-information-on-native-client" id="id2">Where can I get more information on Native Client?</a></li> 18<li><a class="reference internal" href="#what-people-are-you-looking-for" id="id3">What people are you looking for?</a></li> 19<li><a class="reference internal" href="#how-do-i-sign-up" id="id4">How do I sign up?</a></li> 20<li><a class="reference internal" href="#what-is-the-process-of-participating" id="id5">What is the process of participating?</a></li> 21<li><a class="reference internal" href="#how-many-prizes-are-there-what-are-the-prizes" id="id6">How many prizes are there? What are the prizes?</a></li> 22<li><a class="reference internal" href="#can-i-sign-up-as-a-team-how-many-people-can-be-a-member-of-my-team" id="id7">Can I sign up as a team? How many people can be a member of my team?</a></li> 23<li><a class="reference internal" href="#what-will-i-need-to-do-to-win" id="id8">What will I need to do to win?</a></li> 24<li><a class="reference internal" href="#who-is-going-to-judge-these-entries-who-are-these-people" id="id9">Who is going to judge these entries? Who are these people?</a></li> 25<li><a class="reference internal" href="#when-can-i-start-submitting-issues" id="id10">When can I start submitting issues?</a></li> 26<li><a class="reference internal" href="#registration-does-not-work-for-me-what-can-i-do" id="id11">Registration does not work for me—what can I do?</a></li> 27<li><a class="reference internal" href="#i-registered-as-a-team-but-i-want-to-change-the-team-composition-by-adding-or-removing-members-what-should-i-do" id="id12">I registered as a team but I want to change the team composition by adding or removing members. What should I do?</a></li> 28<li><a class="reference internal" href="#i-have-a-previous-engagement-and-i-cannot-sign-up-until-after-the-competition-starts-is-this-ok" id="id13">I have a previous engagement and I cannot sign up until after the competition starts. Is this ok?</a></li> 29<li><a class="reference internal" href="#my-team-has-accepted-the-terms-and-conditions-except-for-one-person-who-is-unavailable-whose-email-was-misspelled-etc-what-can-i-do" id="id14">My team has accepted the Terms and Conditions except for one person who is unavailable / whose email was misspelled / etc. What can I do?</a></li> 30<li><a class="reference internal" href="#can-i-enter-multiple-times" id="id15">Can I enter multiple times?</a></li> 31<li><a class="reference internal" href="#why-do-you-need-a-prize-recipient" id="id16">Why do you need a prize recipient?</a></li> 32<li><a class="reference internal" href="#we-want-to-change-the-prize-recipient-what-can-we-do" id="id17">We want to change the prize recipient. What can we do?</a></li> 33<li><a class="reference internal" href="#i-want-to-remain-anonymous-during-the-contest-is-this-possible" id="id18">I want to remain anonymous during the contest. Is this possible?</a></li> 34<li><a class="reference internal" href="#one-of-my-professors-friends-is-a-judge-can-i-participate" id="id19">One of my professors / friends is a judge. Can I participate?</a></li> 35<li><a class="reference internal" href="#can-my-company-be-registered-as-an-entrant" id="id20">Can my company be registered as an entrant?</a></li> 36<li><a class="reference internal" href="#i-never-signed-up-for-this-contest-but-i-got-an-email-from-you-what-is-this-about" id="id21">I never signed up for this contest, but I got an email from you. What is this about?</a></li> 37<li><a class="reference internal" href="#i-tried-to-sign-up-and-it-seems-someone-who-wants-to-be-a-member-of-my-team-has-already-registered-with-another-team-what-can-we-do" id="id22">I tried to sign up and it seems someone who wants to be a member of my team has already registered with another team. What can we do?</a></li> 38<li><a class="reference internal" href="#i-lost-or-never-got-the-email-asking-me-to-confirm-the-terms-and-conditions-what-can-i-do" id="id23">I lost or never got the email asking me to confirm the Terms and Conditions. What can I do?</a></li> 39<li><a class="reference internal" href="#one-of-our-team-members-rejected-the-terms-and-conditions-what-can-we-do" id="id24">One of our team members rejected the Terms and Conditions. What can we do?</a></li> 40<li><a class="reference internal" href="#how-are-you-going-to-evaluate-the-submissions" id="id25">How are you going to evaluate the submissions?</a></li> 41<li><a class="reference internal" href="#can-i-include-issues-i-submitted-before-the-contest" id="id26">Can I include issues I submitted before the contest?</a></li> 42<li><a class="reference internal" href="#what-is-the-difference-between-exploit-issue-and-summary" id="id27">What is the difference between exploit, issue and summary?</a></li> 43<li><a class="reference internal" href="#what-issues-should-i-include-in-the-summary" id="id28">What issues should I include in the summary?</a></li> 44<li><a class="reference internal" href="#why-are-you-asking-for-the-top-10-issues-only" id="id29">Why are you asking for the top 10 issues only?</a></li> 45<li><a class="reference internal" href="#my-english-is-not-great-will-this-count-against-me-in-the-judging-process" id="id30">My English is not great—will this count against me in the judging process?</a></li> 46<li><a class="reference internal" href="#what-information-do-i-need-to-include-in-the-issue-submission" id="id31">What information do I need to include in the issue submission?</a></li> 47<li><a class="reference internal" href="#how-do-i-contest-a-decision-that-a-bug-is-a-duplicate" id="id32">How do I contest a decision that a bug is a duplicate?</a></li> 48<li><a class="reference internal" href="#why-is-the-native-client-team-updating-the-source-code-during-the-contest" id="id33">Why is the Native Client team updating the source code during the contest?</a></li> 49<li><a class="reference internal" href="#i-forgot-to-include-something-in-the-summary-what-can-i-do" id="id34">I forgot to include something in the summary—what can I do?</a></li> 50<li><a class="reference internal" href="#someone-from-our-team-submitted-a-summary-on-behalf-of-our-team-without-consulting-with-everyone-else-how-can-we-ensure-that-the-judges-will-use-the-previous-summary-and-not-the-last-one" id="id35">Someone from our team submitted a summary on behalf of our team without consulting with everyone else. How can we ensure that the judges will use the previous summary and not the last one?</a></li> 51<li><a class="reference internal" href="#will-you-be-evaluating-each-exploit-separately-for-every-one-of-the-criteria" id="id36">Will you be evaluating each exploit separately for every one of the criteria?</a></li> 52<li><a class="reference internal" href="#i-only-found-one-exploit-but-i-think-it-is-very-good-can-i-still-win" id="id37">I only found one exploit but I think it is very good. Can I still win?</a></li> 53<li><a class="reference internal" href="#how-are-you-going-to-pick-the-winners" id="id38">How are you going to pick the winners?</a></li> 54<li><a class="reference internal" href="#when-and-how-are-we-going-to-find-out-the-results-of-the-contest" id="id39">When and how are we going to find out the results of the contest?</a></li> 55<li><a class="reference internal" href="#what-will-google-do-with-my-data" id="id40">What will Google do with my data?</a></li> 56<li><a class="reference internal" href="#i-have-more-questions-where-can-i-get-a-response" id="id41">I have more questions—where can I get a response?</a></li> 57<li><a class="reference internal" href="#i-like-this-project-are-you-hiring-people-to-work-on-it-full-time" id="id42">I like this project. Are you hiring people to work on it full time?</a></li> 58<li><a class="reference internal" href="#how-can-i-get-involved-in-this-project-besides-the-contest" id="id43">How can I get involved in this project besides the contest?</a></li> 59<li><a class="reference internal" href="#why-is-my-country-province-excluded-from-the-contest" id="id44">Why is my country/province excluded from the contest?</a></li> 60</ul> 61 62</div><h2 id="what-is-this-contest-about">What is this contest about?</h2> 63<p>We launched this contest in order to help make Native Client more 64secure. We invite participants to discover security bugs in our 65technology in order to compete to win cash prizes.</p> 66<h2 id="where-can-i-get-more-information-on-native-client">Where can I get more information on Native Client?</h2> 67<p>You can read our <a class="reference external" href="http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/pubs/archive/34913.pdf">research paper</a> 68(PDF) or visit the site for the <a class="reference external" href="http://code.google.com/p/nativeclient">Native Client open-source project</a>.</p> 69<h2 id="what-people-are-you-looking-for">What people are you looking for?</h2> 70<p>We are not looking for any particular participant profile. Everyone 71who is eligible to participate based on the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> of the contest can sign up.</p> 72<h2 id="how-do-i-sign-up">How do I sign up?</h2> 73<p>The first thing you need to do is to register. Then you and your team 74members (if any) will receive an email from our team asking you to 75review and accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>:doc:` of the contest <contest-terms>`. Once everyone 76from your team has accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> you can start submitting bugs through the Native 77Client issue tracker. You should not submit any bugs as part of your 78contest entries until everyone on your team has accepted the 79<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>, as those bugs will not be 80eligible for consideration in the contest.</p> 81<h2 id="what-is-the-process-of-participating">What is the process of participating?</h2> 82<p>After you register yourself or your team and every member of your team 83has accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>, download 84the latest build of Native Client, attack it, and identify security 85exploits. Submit these bugs through our Native Client Issue Tracker as 86quickly as you can, as you will only get credit for exploits that are 87first reported by yourself or your team. Before the end of the 88contest, you will need to submit a summary with the top 10 exploits 89you identified. Our judges will review submitted summaries and will 90select the top 5 contestants.</p> 91<h2 id="how-many-prizes-are-there-what-are-the-prizes"><span id="contest-faq-prizes"></span>How many prizes are there? What are the prizes?</h2> 92<p>There are five cash prizes: The first prize is $8,192, the second 93prize $4,096, the third prize is $2,048, the fourth prize is $1,024 94and the fifth prize is $1,024. All amounts are in USD.</p> 95<h2 id="can-i-sign-up-as-a-team-how-many-people-can-be-a-member-of-my-team">Can I sign up as a team? How many people can be a member of my team?</h2> 96<p>You can sign up as a team. There is no limit to how many people can 97participate in your team. However we recommend that you keep the size 98of your team small so as to be able to better coordinate during the 99contest.</p> 100<h2 id="what-will-i-need-to-do-to-win">What will I need to do to win?</h2> 101<p>To participate, you will need to test the Native Client builds, 102identify security exploits which affect the current Native Client 103build at the time of submission and report them to our team. Our 104judges will review your entry. If you are one of the top five 105participants selected by the judges and satisfy the requirements for 106eligibility, then you will win a cash prize. For more information on 107how to participate and how your entry will be evaluated please review 108our detailed <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 109<h2 id="who-is-going-to-judge-these-entries-who-are-these-people">Who is going to judge these entries? Who are these people?</h2> 110<p>Google has recruited a group of distinguished security experts to 111serve as judges for this contest:</p> 112<ul class="small-gap"> 113<li>Edward Felten — jury chair (Princeton)</li> 114<li>Alex Halderman (Michigan)</li> 115<li>Brad Karp (University College London)</li> 116<li>Greg Morrisett (Harvard)</li> 117<li>Niels Provos (Google)</li> 118<li>Stefan Savage (UCSD)</li> 119<li>Dan Wallach (Rice)</li> 120<li>Bennet Yee (Google)</li> 121<li>Nickolai Zeldovich (MIT)</li> 122</ul> 123<p>Check out the <a class="reference internal" href="/native-client/community/security-contest/index.html#contest-judges"><em>Judges info</em></a> to learn more about 124their careers and contributions to the security community.</p> 125<h2 id="when-can-i-start-submitting-issues">When can I start submitting issues?</h2> 126<p>You can start submitting issues after you and your team members (if 127any) have completed the registration process and accepted the 128<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 129<h2 id="registration-does-not-work-for-me-what-can-i-do">Registration does not work for me—what can I do?</h2> 130<p>We recommend that you post this problem at the Google Group. Once you 131do so, a member from our team will reach out to you to try to diagnose 132the issue. We will try to help you out; keep in mind though that we 133can not be responsible for the inability of a participant to register.</p> 134<h2 id="i-registered-as-a-team-but-i-want-to-change-the-team-composition-by-adding-or-removing-members-what-should-i-do">I registered as a team but I want to change the team composition by adding or removing members. What should I do?</h2> 135<p>Please reply to one of the registration email messages you received 136(it should be sent to <a class="reference external" href="mailto:nacl-security-contest%40google.com">nacl-security-contest<span>@</span>google<span>.</span>com</a>) and indicate 137the changes you’d like to make. Please note that neither the team name 138nor team membership can be changed once all members have accepted the 139<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 140<h2 id="i-have-a-previous-engagement-and-i-cannot-sign-up-until-after-the-competition-starts-is-this-ok">I have a previous engagement and I cannot sign up until after the competition starts. Is this ok?</h2> 141<p>You can sign up until the last day of the contest May 1425th, 2009. However, keep in mind that while you can submit bugs 143through the Native Client Issue Tracker, none of these will be taken 144into account unless you (and all your team members) have completed the 145registration process prior to submitting any bugs.</p> 146<h2 id="my-team-has-accepted-the-terms-and-conditions-except-for-one-person-who-is-unavailable-whose-email-was-misspelled-etc-what-can-i-do">My team has accepted the Terms and Conditions except for one person who is unavailable / whose email was misspelled / etc. What can I do?</h2> 147<p>To make edits to your team’s composition, or to update the contact 148information of a team member, you will need to reply to one of the 149registration emails you received (it should be sent to 150<a class="reference external" href="mailto:nacl-security-contest%40google.com">nacl-security-contest<span>@</span>google<span>.</span>com</a>) and indicate the changes you’d like 151to make. Please note that this will mean that your team members will 152receive an email notifying them of the changes in the team’s 153composition and asking them to re-accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and 154Conditions</em></a>. All team members will need to re-accept 155the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> for the team to be 156considered as active.</p> 157<h2 id="can-i-enter-multiple-times">Can I enter multiple times?</h2> 158<p>No, you cannot enter multiple times. If you register as an individual 159you can not also register on a team and if you are on a team you can 160not also be on another team.</p> 161<h2 id="why-do-you-need-a-prize-recipient">Why do you need a prize recipient?</h2> 162<p>Google will not be responsible for the division of any prize money 163between members of a potential winning team. Instead Google will 164deliver the prize to one member indicated by the team. The team is 165solely responsible for managing the logistics of distributing the 166prize among team members. This is why Google asks all participating 167teams to identify a prize recipient.</p> 168<h2 id="we-want-to-change-the-prize-recipient-what-can-we-do">We want to change the prize recipient. What can we do?</h2> 169<p>To make edits to the prize recipient before all team members have 170accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>, you will 171need to reply to one of the registration emails you received (it 172should be sent to <a class="reference external" href="mailto:nacl-security-contest%40google.com">nacl-security-contest<span>@</span>google<span>.</span>com</a>) and indicate the 173changes you’d like to make. Please note that this will mean that your 174team members will receive an email notifying them of the change and 175asking them to re-accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>. All team members will need to re-accept the 176<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> for the team to be 177considered registered. After all team members have accepted the 178<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>, there can be no changes 179to the prize recipient.</p> 180<h2 id="i-want-to-remain-anonymous-during-the-contest-is-this-possible">I want to remain anonymous during the contest. Is this possible?</h2> 181<p>Yes. However, you will still need to provide us with your email 182address to register. After the contest ends and if you are one of the 183top 5 participants, to claim your prize, you and all of your team 184members (if any) will need to submit to Google all necessary tax and 185legal information that Google will need to comply with US and 186international legal and tax regulations.</p> 187<h2 id="one-of-my-professors-friends-is-a-judge-can-i-participate">One of my professors / friends is a judge. Can I participate?</h2> 188<p>Yes, you can participate.</p> 189<h2 id="can-my-company-be-registered-as-an-entrant">Can my company be registered as an entrant?</h2> 190<p>No, this is not possible under our <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 191<h2 id="i-never-signed-up-for-this-contest-but-i-got-an-email-from-you-what-is-this-about">I never signed up for this contest, but I got an email from you. What is this about?</h2> 192<p>You have probably received an e-mail identifying you as a member of 193team that another person has created. In our email, we identified the 194email address of a person who registered you as a teammate in the 195Native Client Security Contest. If you want to participate in this 196person’s team, then accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> by clicking on the link included in the email. If you 197do not wish to participate in the contest or you want to do so as a 198member of a different team, then you can remove yourself from the list 199of team members of that particular team.</p> 200<h2 id="i-tried-to-sign-up-and-it-seems-someone-who-wants-to-be-a-member-of-my-team-has-already-registered-with-another-team-what-can-we-do">I tried to sign up and it seems someone who wants to be a member of my team has already registered with another team. What can we do?</h2> 201<p>If everyone in your potential teammate’s original team (including 202himself/herself) has accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> of the contest, then unfortunately you will have to 203look for other potential partners. Otherwise, your potential teammate 204can remove himself from the other team. All he/she will need to do is 205to reply to one of the registration emails he/she received (it should 206be sent to <a class="reference external" href="mailto:nacl-security-contest%40google.com">nacl-security-contest<span>@</span>google<span>.</span>com</a>) and indicate the changes 207to be made. Please note that this will mean that his/her team members 208will receive an email notifying them of the changes in the team’s 209composition and asking them to re-accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and 210Conditions</em></a>. All team members of that team will need 211to re-accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> for that 212team to be considered as active.</p> 213<h2 id="i-lost-or-never-got-the-email-asking-me-to-confirm-the-terms-and-conditions-what-can-i-do">I lost or never got the email asking me to confirm the Terms and Conditions. What can I do?</h2> 214<p>Don’t worry, just send us an email at <a class="reference external" href="mailto:nacl-security-contest%40google.com">nacl-security-contest<span>@</span>google<span>.</span>com</a> 215and we will send you the link you need.</p> 216<h2 id="one-of-our-team-members-rejected-the-terms-and-conditions-what-can-we-do">One of our team members rejected the Terms and Conditions. What can we do?</h2> 217<p>Your team is now considered to be invalid. If this rejection happened 218by accident, please restart the registration process. If it was 219deliberate then create a new team with teammates who are willing to 220accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>. No one can 221participate in the contest unless they have accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms 222and Conditions</em></a> and no team can participate unless all 223team members have accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 224<h2 id="how-are-you-going-to-evaluate-the-submissions">How are you going to evaluate the submissions?</h2> 225<p>The judges will evaluate each Summary based on the following 226criteria: a) Quality (Severity, Scope, Reliability and Style) and b) 227Quantity. Please review the judging criteria in the contest 228<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> for more information.</p> 229<h2 id="can-i-include-issues-i-submitted-before-the-contest">Can I include issues I submitted before the contest?</h2> 230<p>No, you can not.</p> 231<h2 id="what-is-the-difference-between-exploit-issue-and-summary">What is the difference between exploit, issue and summary?</h2> 232<p>An exploit becomes an issue once you submit it through the Native 233Client issue tracker. A summary can include multiple issues but not 234more than 10.</p> 235<h2 id="what-issues-should-i-include-in-the-summary">What issues should I include in the summary?</h2> 236<p>You should include a maximum of 10 issues that you and your team 237members (if any) submitted to the Native Client Issue tracker. We 238recommend that you carefully review the judging criteria in the 239<a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> to identify which bugs are 240more likely to be perceived as high impact from our judges and could 241help you win one of the five cash prizes. Do not include issues that 242have been marked as duplicates or unverifiable, as these will not be 243taken into account by our judges.</p> 244<h2 id="why-are-you-asking-for-the-top-10-issues-only">Why are you asking for the top 10 issues only?</h2> 245<p>We want to make sure that we use our judges’ time wisely. Rather than 246having them review hundreds of similar or small scale bugs, sometimes 247identified with the same automatic process, we are limiting the number 248of issues that each participant can submit in his/her/their summary.</p> 249<h2 id="my-english-is-not-great-will-this-count-against-me-in-the-judging-process">My English is not great—will this count against me in the judging process?</h2> 250<p>Entries in languages other than in English or entries that are deemed 251incomprehensible by the judges will not be reviewed. We do not plan to 252penalize summaries for spelling or grammar mistakes, but please make 253your descriptions as clear as possible.</p> 254<h2 id="what-information-do-i-need-to-include-in-the-issue-submission">What information do I need to include in the issue submission?</h2> 255<p>Please review the “Minimum requirements for issues” section of 256contest’s <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>. You will find a 257list of all the information you will need to include in every 258submitted issue. Failure to provide this information might make the 259submitted issue invalid for the purposes of this contest.</p> 260<h2 id="how-do-i-contest-a-decision-that-a-bug-is-a-duplicate">How do I contest a decision that a bug is a duplicate?</h2> 261<p>Please highlight this in our Google Group and a member of our team 262will get in touch with you.</p> 263<h2 id="why-is-the-native-client-team-updating-the-source-code-during-the-contest">Why is the Native Client team updating the source code during the contest?</h2> 264<p>We are updating Native Client’s source code to fix bugs reported by 265contest participants or exploits identified by our team. Our goal is 266to protect contestants and other users of the Native Client software 267from exploits that could damage their system. In addition, by updating 268our builds, we will be providing you with more opportunities to find 269new security bugs. Finally, we believe this will make the contest more 270interesting by continuously raising the bar of bug finding.</p> 271<h2 id="i-forgot-to-include-something-in-the-summary-what-can-i-do">I forgot to include something in the summary—what can I do?</h2> 272<p>If the contest has not ended, you may submit an updated summary. You 273may not submit an updated summary once the contest has ended.</p> 274<h2 id="someone-from-our-team-submitted-a-summary-on-behalf-of-our-team-without-consulting-with-everyone-else-how-can-we-ensure-that-the-judges-will-use-the-previous-summary-and-not-the-last-one">Someone from our team submitted a summary on behalf of our team without consulting with everyone else. How can we ensure that the judges will use the previous summary and not the last one?</h2> 275<p>If your team member submitted his / her version of the team’s summary 276before the end date of the contest, and if this is the last summary 277that was submitted from your team, then the Judges will disregard all 278previous versions of your summary and will only review this last 279one. If the contest has not ended, you may resubmit a previous summary 280to override the first.</p> 281<h2 id="will-you-be-evaluating-each-exploit-separately-for-every-one-of-the-criteria">Will you be evaluating each exploit separately for every one of the criteria?</h2> 282<p>We will use our criteria to evaluate submitted summaries, not 283individual exploits.</p> 284<h2 id="i-only-found-one-exploit-but-i-think-it-is-very-good-can-i-still-win">I only found one exploit but I think it is very good. Can I still win?</h2> 285<p>Yes. Quantity is only one of the criteria we use to evaluate submitted 286summaries.</p> 287<h2 id="how-are-you-going-to-pick-the-winners">How are you going to pick the winners?</h2> 288<p>After the contest ends, all submitted Summaries will be judged by a 289panel of at least three judges. The judges will evaluate each Summary 290based on the following criteria: a) Quality (Severity, Scope, 291Reliability and Style) and b) Quantity. Each panel will evaluate a 292number of the submitted summaries and will select the highest ranking 293Summaries to move to the next level of judging. Those top Summaries 294will then be evaluated by all Judges using the same Criteria, and the 295top five Summaries will be selected as potential winners. For more 296information on the judging criteria and the judging process please 297review the relevant section of the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> 298<h2 id="when-and-how-are-we-going-to-find-out-the-results-of-the-contest">When and how are we going to find out the results of the contest?</h2> 299<p>We will contact all prospective winners at the email address provided 300to us at the registration process. You may request a list of winners 301after December 7th, 2009 by writing to: Native Client Security Contest 302Google Inc. 1600 Amphitheater Parkway Mountain View, CA 94043 USA</p> 303<h2 id="what-will-google-do-with-my-data">What will Google do with my data?</h2> 304<p>The personal data you provided to Google during the Contest will be 305stored and processed in the US within the context of the Contest. We 306will maintain your data in the way described at the Google Privacy 307Policy found at <a class="reference external" href="http://www.google.com/privacypolicy.html">http://www.google.com/privacypolicy.html</a>. Google may 308use your data to verify your identity, postal address and telephone 309number in the event you qualify for a prize. You have a right to 310access and withdraw your personal data. To exercise this right, you 311may write to: Native Client Security Contest, Google Inc., 1600 312Amphitheater Parkway, Mountain View, CA 94043, USA.</p> 313<h2 id="i-have-more-questions-where-can-i-get-a-response">I have more questions—where can I get a response?</h2> 314<p>We recommend to ask any additional questions you might have in the 315Google Group. Members from our team will be monitoring the group and 316will respond to your question there, to benefit other contest 317participants.</p> 318<h2 id="i-like-this-project-are-you-hiring-people-to-work-on-it-full-time">I like this project. Are you hiring people to work on it full time?</h2> 319<p>At Google we are always looking for great people. Please review our 320current openings at www.google.com/jobs.</p> 321<h2 id="how-can-i-get-involved-in-this-project-besides-the-contest">How can I get involved in this project besides the contest?</h2> 322<p>Thank you for your interest in Native Client. You can help us by:</p> 323<ul class="small-gap"> 324<li>Identifying bugs</li> 325<li>Porting OS libraries</li> 326<li>Writing apps</li> 327</ul> 328<p>We would also like to see you participate in our discussion group.</p> 329<h2 id="why-is-my-country-province-excluded-from-the-contest">Why is my country/province excluded from the contest?</h2> 330<p>While we seek to make this contest open worldwide, we cannot open it 331to residents of Cuba, Iran, Syria, North Korea, Sudan, or Myanmar 332(Burma) because of U.S. laws. In addition, the contest is not open to 333residents of Brazil, Italy, or Quebec because of local 334restrictions. For more information on eligibility, see the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms 335and Conditions</em></a>.</p> 336</section> 337 338{{/partials.standard_nacl_article}} 339