OLD | NEW |
(Empty) | |
| 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-fa
q"></span>Security Contest FAQ</h1> |
| 5 <aside class="caution"> |
| 6 The Native Client Security Contest has ended—check out the |
| 7 <a class="reference internal" href="/native-client/community/security-contest/in
dex.html#contest-winners"><em>winning submissions</em></a>. We welcome your |
| 8 continued 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 |
| 10 participating in the <a class="reference external" href="http://groups.google.co
m/group/native-client-discuss">Native Client discussion group</a>. |
| 11 </aside> |
| 12 <p>This FAQ is provided for reference only. For the complete official |
| 13 contest rules, see the Terms and Conditions.</p> |
| 14 <div class="contents local topic" id="contents"> |
| 15 <ul class="small-gap"> |
| 16 <li><a class="reference internal" href="#what-is-this-contest-about" id="id1">Wh
at is this contest about?</a></li> |
| 17 <li><a class="reference internal" href="#where-can-i-get-more-information-on-nat
ive-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="id
3">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 sig
n up?</a></li> |
| 20 <li><a class="reference internal" href="#what-is-the-process-of-participating" i
d="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 c
an 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 p
eople?</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-ch
ange-the-team-composition-by-adding-or-removing-members-what-should-i-do" id="id
12">I registered as a team but I want to change the team composition by adding o
r removing members. What should I do?</a></li> |
| 28 <li><a class="reference internal" href="#i-have-a-previous-engagement-and-i-cann
ot-sign-up-until-after-the-competition-starts-is-this-ok" id="id13">I have a pre
vious engagement and I cannot sign up until after the competition starts. Is thi
s ok?</a></li> |
| 29 <li><a class="reference internal" href="#my-team-has-accepted-the-terms-and-cond
itions-except-for-one-person-who-is-unavailable-whose-email-was-misspelled-etc-w
hat-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">C
an 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-w
hat-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-c
ontest-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 p
articipate?</a></li> |
| 35 <li><a class="reference internal" href="#can-my-company-be-registered-as-an-entr
ant" 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-wh
at-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 go
t the email asking me to confirm the Terms and Conditions. What can I do?</a></l
i> |
| 39 <li><a class="reference internal" href="#one-of-our-team-members-rejected-the-te
rms-and-conditions-what-can-we-do" id="id24">One of our team members rejected th
e Terms and Conditions. What can we do?</a></li> |
| 40 <li><a class="reference internal" href="#how-are-you-going-to-evaluate-the-submi
ssions" 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 s
ummary?</a></li> |
| 43 <li><a class="reference internal" href="#what-issues-should-i-include-in-the-sum
mary" 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-issue
s-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-i
n-the-issue-submission" id="id31">What information do I need to include in the i
ssue 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 upda
ting the source code during the contest?</a></li> |
| 49 <li><a class="reference internal" href="#i-forgot-to-include-something-in-the-su
mmary-what-can-i-do" id="id34">I forgot to include something in the summary̵
2;what can I do?</a></li> |
| 50 <li><a class="reference internal" href="#someone-from-our-team-submitted-a-summa
ry-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">S
omeone from our team submitted a summary on behalf of our team without consultin
g with everyone else. How can we ensure that the judges will use the previous su
mmary and not the last one?</a></li> |
| 51 <li><a class="reference internal" href="#will-you-be-evaluating-each-exploit-sep
arately-for-every-one-of-the-criteria" id="id36">Will you be evaluating each exp
loit 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-t
he-results-of-the-contest" id="id39">When and how are we going to find out the r
esults of the contest?</a></li> |
| 55 <li><a class="reference internal" href="#what-will-google-do-with-my-data" id="i
d40">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-peop
le-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 th
e contest?</a></li> |
| 59 <li><a class="reference internal" href="#why-is-my-country-province-excluded-fro
m-the-contest" id="id44">Why is my country/province excluded from the contest?</
a></li> |
| 60 </ul> |
| 61 </div> |
| 62 <section id="what-is-this-contest-about"> |
| 63 <h2 id="what-is-this-contest-about">What is this contest about?</h2> |
| 64 <p>We launched this contest in order to help make Native Client more |
| 65 secure. We invite participants to discover security bugs in our |
| 66 technology in order to compete to win cash prizes.</p> |
| 67 </section><section id="where-can-i-get-more-information-on-native-client"> |
| 68 <h2 id="where-can-i-get-more-information-on-native-client">Where can I get more
information on Native Client?</h2> |
| 69 <p>You can read our <a class="reference external" href="http://static.googleuser
content.com/external_content/untrusted_dlcp/research.google.com/en/us/pubs/archi
ve/34913.pdf">research paper</a> |
| 70 (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> |
| 71 </section><section id="what-people-are-you-looking-for"> |
| 72 <h2 id="what-people-are-you-looking-for">What people are you looking for?</h2> |
| 73 <p>We are not looking for any particular participant profile. Everyone |
| 74 who is eligible to participate based on the <a class="reference internal" href="
/native-client/community/security-contest/contest-terms.html"><em>Terms and Cond
itions</em></a> of the contest can sign up.</p> |
| 75 </section><section id="how-do-i-sign-up"> |
| 76 <h2 id="how-do-i-sign-up">How do I sign up?</h2> |
| 77 <p>The first thing you need to do is to register. Then you and your team |
| 78 members (if any) will receive an email from our team asking you to |
| 79 review and accept the <a class="reference internal" href="/native-client/communi
ty/security-contest/contest-terms.html"><em>Terms and Conditions</em></a>:doc:`
of the contest <contest-terms>`. Once everyone |
| 80 from your team has accepted the <a class="reference internal" href="/native-clie
nt/community/security-contest/contest-terms.html"><em>Terms and Conditions</em><
/a> you can start submitting bugs through the Native |
| 81 Client issue tracker. You should not submit any bugs as part of your |
| 82 contest entries until everyone on your team has accepted the |
| 83 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a>, as those bugs will not be |
| 84 eligible for consideration in the contest.</p> |
| 85 </section><section id="what-is-the-process-of-participating"> |
| 86 <h2 id="what-is-the-process-of-participating">What is the process of participati
ng?</h2> |
| 87 <p>After you register yourself or your team and every member of your team |
| 88 has accepted the <a class="reference internal" href="/native-client/community/se
curity-contest/contest-terms.html"><em>Terms and Conditions</em></a>, download |
| 89 the latest build of Native Client, attack it, and identify security |
| 90 exploits. Submit these bugs through our Native Client Issue Tracker as |
| 91 quickly as you can, as you will only get credit for exploits that are |
| 92 first reported by yourself or your team. Before the end of the |
| 93 contest, you will need to submit a summary with the top 10 exploits |
| 94 you identified. Our judges will review submitted summaries and will |
| 95 select the top 5 contestants.</p> |
| 96 </section><section id="how-many-prizes-are-there-what-are-the-prizes"> |
| 97 <span id="contest-faq-prizes"></span><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> |
| 98 <p>There are five cash prizes: The first prize is $8,192, the second |
| 99 prize $4,096, the third prize is $2,048, the fourth prize is $1,024 |
| 100 and the fifth prize is $1,024. All amounts are in USD.</p> |
| 101 </section><section id="can-i-sign-up-as-a-team-how-many-people-can-be-a-member-o
f-my-team"> |
| 102 <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> |
| 103 <p>You can sign up as a team. There is no limit to how many people can |
| 104 participate in your team. However we recommend that you keep the size |
| 105 of your team small so as to be able to better coordinate during the |
| 106 contest.</p> |
| 107 </section><section id="what-will-i-need-to-do-to-win"> |
| 108 <h2 id="what-will-i-need-to-do-to-win">What will I need to do to win?</h2> |
| 109 <p>To participate, you will need to test the Native Client builds, |
| 110 identify security exploits which affect the current Native Client |
| 111 build at the time of submission and report them to our team. Our |
| 112 judges will review your entry. If you are one of the top five |
| 113 participants selected by the judges and satisfy the requirements for |
| 114 eligibility, then you will win a cash prize. For more information on |
| 115 how to participate and how your entry will be evaluated please review |
| 116 our detailed <a class="reference internal" href="/native-client/community/securi
ty-contest/contest-terms.html"><em>Terms and Conditions</em></a>.</p> |
| 117 </section><section id="who-is-going-to-judge-these-entries-who-are-these-people"
> |
| 118 <h2 id="who-is-going-to-judge-these-entries-who-are-these-people">Who is going t
o judge these entries? Who are these people?</h2> |
| 119 <p>Google has recruited a group of distinguished security experts to |
| 120 serve as judges for this contest:</p> |
| 121 <ul class="small-gap"> |
| 122 <li>Edward Felten — jury chair (Princeton)</li> |
| 123 <li>Alex Halderman (Michigan)</li> |
| 124 <li>Brad Karp (University College London)</li> |
| 125 <li>Greg Morrisett (Harvard)</li> |
| 126 <li>Niels Provos (Google)</li> |
| 127 <li>Stefan Savage (UCSD)</li> |
| 128 <li>Dan Wallach (Rice)</li> |
| 129 <li>Bennet Yee (Google)</li> |
| 130 <li>Nickolai Zeldovich (MIT)</li> |
| 131 </ul> |
| 132 <p>Check out the <a class="reference internal" href="/native-client/community/se
curity-contest/index.html#contest-judges"><em>Judges info</em></a> to learn more
about |
| 133 their careers and contributions to the security community.</p> |
| 134 </section><section id="when-can-i-start-submitting-issues"> |
| 135 <h2 id="when-can-i-start-submitting-issues">When can I start submitting issues?<
/h2> |
| 136 <p>You can start submitting issues after you and your team members (if |
| 137 any) have completed the registration process and accepted the |
| 138 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a>.</p> |
| 139 </section><section id="registration-does-not-work-for-me-what-can-i-do"> |
| 140 <h2 id="registration-does-not-work-for-me-what-can-i-do">Registration does not w
ork for me—what can I do?</h2> |
| 141 <p>We recommend that you post this problem at the Google Group. Once you |
| 142 do so, a member from our team will reach out to you to try to diagnose |
| 143 the issue. We will try to help you out; keep in mind though that we |
| 144 can not be responsible for the inability of a participant to register.</p> |
| 145 </section><section id="i-registered-as-a-team-but-i-want-to-change-the-team-comp
osition-by-adding-or-removing-members-what-should-i-do"> |
| 146 <h2 id="i-registered-as-a-team-but-i-want-to-change-the-team-composition-by-addi
ng-or-removing-members-what-should-i-do">I registered as a team but I want to ch
ange the team composition by adding or removing members. What should I do?</h2> |
| 147 <p>Please reply to one of the registration email messages you received |
| 148 (it should be sent to <a class="reference external" href="mailto:nacl-security-c
ontest%40google.com">nacl-security-contest<span>@</span>goog
le<span>.</span>com</a>) and indicate |
| 149 the changes you’d like to make. Please note that neither the team name |
| 150 nor team membership can be changed once all members have accepted the |
| 151 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a>.</p> |
| 152 </section><section id="i-have-a-previous-engagement-and-i-cannot-sign-up-until-a
fter-the-competition-starts-is-this-ok"> |
| 153 <h2 id="i-have-a-previous-engagement-and-i-cannot-sign-up-until-after-the-compet
ition-starts-is-this-ok">I have a previous engagement and I cannot sign up until
after the competition starts. Is this ok?</h2> |
| 154 <p>You can sign up until the last day of the contest May |
| 155 5th, 2009. However, keep in mind that while you can submit bugs |
| 156 through the Native Client Issue Tracker, none of these will be taken |
| 157 into account unless you (and all your team members) have completed the |
| 158 registration process prior to submitting any bugs.</p> |
| 159 </section><section 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"> |
| 160 <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 accepte
d the Terms and Conditions except for one person who is unavailable / whose emai
l was misspelled / etc. What can I do?</h2> |
| 161 <p>To make edits to your team’s composition, or to update the contact |
| 162 information of a team member, you will need to reply to one of the |
| 163 registration emails you received (it should be sent to |
| 164 <a class="reference external" href="mailto:nacl-security-contest%40g
oogle.com">nacl-security-contest<span>@</span>google<span>.</span>co
m</a>) and indicate the changes you’d like |
| 165 to make. Please note that this will mean that your team members will |
| 166 receive an email notifying them of the changes in the team’s |
| 167 composition and asking them to re-accept the <a class="reference internal" href=
"/native-client/community/security-contest/contest-terms.html"><em>Terms and |
| 168 Conditions</em></a>. All team members will need to re-accept |
| 169 the <a class="reference internal" href="/native-client/community/security-contes
t/contest-terms.html"><em>Terms and Conditions</em></a> for the team to be |
| 170 considered as active.</p> |
| 171 </section><section id="can-i-enter-multiple-times"> |
| 172 <h2 id="can-i-enter-multiple-times">Can I enter multiple times?</h2> |
| 173 <p>No, you cannot enter multiple times. If you register as an individual |
| 174 you can not also register on a team and if you are on a team you can |
| 175 not also be on another team.</p> |
| 176 </section><section id="why-do-you-need-a-prize-recipient"> |
| 177 <h2 id="why-do-you-need-a-prize-recipient">Why do you need a prize recipient?</h
2> |
| 178 <p>Google will not be responsible for the division of any prize money |
| 179 between members of a potential winning team. Instead Google will |
| 180 deliver the prize to one member indicated by the team. The team is |
| 181 solely responsible for managing the logistics of distributing the |
| 182 prize among team members. This is why Google asks all participating |
| 183 teams to identify a prize recipient.</p> |
| 184 </section><section id="we-want-to-change-the-prize-recipient-what-can-we-do"> |
| 185 <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> |
| 186 <p>To make edits to the prize recipient before all team members have |
| 187 accepted the <a class="reference internal" href="/native-client/community/securi
ty-contest/contest-terms.html"><em>Terms and Conditions</em></a>, you will |
| 188 need to reply to one of the registration emails you received (it |
| 189 should be sent to <a class="reference external" href="mailto:nacl-security-conte
st%40google.com">nacl-security-contest<span>@</span>google<s
pan>.</span>com</a>) and indicate the |
| 190 changes you’d like to make. Please note that this will mean that your |
| 191 team members will receive an email notifying them of the change and |
| 192 asking 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 |
| 193 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a> for the team to be |
| 194 considered registered. After all team members have accepted the |
| 195 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a>, there can be no changes |
| 196 to the prize recipient.</p> |
| 197 </section><section id="i-want-to-remain-anonymous-during-the-contest-is-this-pos
sible"> |
| 198 <h2 id="i-want-to-remain-anonymous-during-the-contest-is-this-possible">I want t
o remain anonymous during the contest. Is this possible?</h2> |
| 199 <p>Yes. However, you will still need to provide us with your email |
| 200 address to register. After the contest ends and if you are one of the |
| 201 top 5 participants, to claim your prize, you and all of your team |
| 202 members (if any) will need to submit to Google all necessary tax and |
| 203 legal information that Google will need to comply with US and |
| 204 international legal and tax regulations.</p> |
| 205 </section><section id="one-of-my-professors-friends-is-a-judge-can-i-participate
"> |
| 206 <h2 id="one-of-my-professors-friends-is-a-judge-can-i-participate">One of my pro
fessors / friends is a judge. Can I participate?</h2> |
| 207 <p>Yes, you can participate.</p> |
| 208 </section><section id="can-my-company-be-registered-as-an-entrant"> |
| 209 <h2 id="can-my-company-be-registered-as-an-entrant">Can my company be registered
as an entrant?</h2> |
| 210 <p>No, this is not possible under our <a class="reference internal" href="/nativ
e-client/community/security-contest/contest-terms.html"><em>Terms and Conditions
</em></a>.</p> |
| 211 </section><section id="i-never-signed-up-for-this-contest-but-i-got-an-email-fro
m-you-what-is-this-about"> |
| 212 <h2 id="i-never-signed-up-for-this-contest-but-i-got-an-email-from-you-what-is-t
his-about">I never signed up for this contest, but I got an email from you. What
is this about?</h2> |
| 213 <p>You have probably received an e-mail identifying you as a member of |
| 214 team that another person has created. In our email, we identified the |
| 215 email address of a person who registered you as a teammate in the |
| 216 Native Client Security Contest. If you want to participate in this |
| 217 person’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 |
| 218 do not wish to participate in the contest or you want to do so as a |
| 219 member of a different team, then you can remove yourself from the list |
| 220 of team members of that particular team.</p> |
| 221 </section><section 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"> |
| 222 <h2 id="i-tried-to-sign-up-and-it-seems-someone-who-wants-to-be-a-member-of-my-t
eam-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> |
| 223 <p>If everyone in your potential teammate’s original team (including |
| 224 himself/herself) has accepted the <a class="reference internal" href="/native-cl
ient/community/security-contest/contest-terms.html"><em>Terms and Conditions</em
></a> of the contest, then unfortunately you will have to |
| 225 look for other potential partners. Otherwise, your potential teammate |
| 226 can remove himself from the other team. All he/she will need to do is |
| 227 to reply to one of the registration emails he/she received (it should |
| 228 be sent to <a class="reference external" href="mailto:nacl-security-contest%
40google.com">nacl-security-contest<span>@</span>google<span>
6;</span>com</a>) and indicate the changes |
| 229 to be made. Please note that this will mean that his/her team members |
| 230 will receive an email notifying them of the changes in the team’s |
| 231 composition and asking them to re-accept the <a class="reference internal" href=
"/native-client/community/security-contest/contest-terms.html"><em>Terms and |
| 232 Conditions</em></a>. All team members of that team will need |
| 233 to re-accept the <a class="reference internal" href="/native-client/community/se
curity-contest/contest-terms.html"><em>Terms and Conditions</em></a> for that |
| 234 team to be considered as active.</p> |
| 235 </section><section id="i-lost-or-never-got-the-email-asking-me-to-confirm-the-te
rms-and-conditions-what-can-i-do"> |
| 236 <h2 id="i-lost-or-never-got-the-email-asking-me-to-confirm-the-terms-and-conditi
ons-what-can-i-do">I lost or never got the email asking me to confirm the Terms
and Conditions. What can I do?</h2> |
| 237 <p>Don’t worry, just send us an email at <a class="reference external" hre
f="mailto:nacl-security-contest%40google.com">nacl-security-cont
est<span>@</span>google<span>.</span>com</a> |
| 238 and we will send you the link you need.</p> |
| 239 </section><section id="one-of-our-team-members-rejected-the-terms-and-conditions
-what-can-we-do"> |
| 240 <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
> |
| 241 <p>Your team is now considered to be invalid. If this rejection happened |
| 242 by accident, please restart the registration process. If it was |
| 243 deliberate then create a new team with teammates who are willing to |
| 244 accept the <a class="reference internal" href="/native-client/community/security
-contest/contest-terms.html"><em>Terms and Conditions</em></a>. No one can |
| 245 participate in the contest unless they have accepted the <a class="reference int
ernal" href="/native-client/community/security-contest/contest-terms.html"><em>T
erms |
| 246 and Conditions</em></a> and no team can participate unless all |
| 247 team members have accepted the <a class="reference internal" href="/native-clien
t/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></
a>.</p> |
| 248 </section><section id="how-are-you-going-to-evaluate-the-submissions"> |
| 249 <h2 id="how-are-you-going-to-evaluate-the-submissions">How are you going to eval
uate the submissions?</h2> |
| 250 <p>The judges will evaluate each Summary based on the following |
| 251 criteria: a) Quality (Severity, Scope, Reliability and Style) and b) |
| 252 Quantity. Please review the judging criteria in the contest |
| 253 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a> for more information.</p> |
| 254 </section><section id="can-i-include-issues-i-submitted-before-the-contest"> |
| 255 <h2 id="can-i-include-issues-i-submitted-before-the-contest">Can I include issue
s I submitted before the contest?</h2> |
| 256 <p>No, you can not.</p> |
| 257 </section><section id="what-is-the-difference-between-exploit-issue-and-summary"
> |
| 258 <h2 id="what-is-the-difference-between-exploit-issue-and-summary">What is the di
fference between exploit, issue and summary?</h2> |
| 259 <p>An exploit becomes an issue once you submit it through the Native |
| 260 Client issue tracker. A summary can include multiple issues but not |
| 261 more than 10.</p> |
| 262 </section><section id="what-issues-should-i-include-in-the-summary"> |
| 263 <h2 id="what-issues-should-i-include-in-the-summary">What issues should I includ
e in the summary?</h2> |
| 264 <p>You should include a maximum of 10 issues that you and your team |
| 265 members (if any) submitted to the Native Client Issue tracker. We |
| 266 recommend that you carefully review the judging criteria in the |
| 267 <a class="reference internal" href="/native-client/community/security-contest/co
ntest-terms.html"><em>Terms and Conditions</em></a> to identify which bugs are |
| 268 more likely to be perceived as high impact from our judges and could |
| 269 help you win one of the five cash prizes. Do not include issues that |
| 270 have been marked as duplicates or unverifiable, as these will not be |
| 271 taken into account by our judges.</p> |
| 272 </section><section id="why-are-you-asking-for-the-top-10-issues-only"> |
| 273 <h2 id="why-are-you-asking-for-the-top-10-issues-only">Why are you asking for th
e top 10 issues only?</h2> |
| 274 <p>We want to make sure that we use our judges’ time wisely. Rather than |
| 275 having them review hundreds of similar or small scale bugs, sometimes |
| 276 identified with the same automatic process, we are limiting the number |
| 277 of issues that each participant can submit in his/her/their summary.</p> |
| 278 </section><section id="my-english-is-not-great-will-this-count-against-me-in-the
-judging-process"> |
| 279 <h2 id="my-english-is-not-great-will-this-count-against-me-in-the-judging-proces
s">My English is not great—will this count against me in the judging proce
ss?</h2> |
| 280 <p>Entries in languages other than in English or entries that are deemed |
| 281 incomprehensible by the judges will not be reviewed. We do not plan to |
| 282 penalize summaries for spelling or grammar mistakes, but please make |
| 283 your descriptions as clear as possible.</p> |
| 284 </section><section id="what-information-do-i-need-to-include-in-the-issue-submis
sion"> |
| 285 <h2 id="what-information-do-i-need-to-include-in-the-issue-submission">What info
rmation do I need to include in the issue submission?</h2> |
| 286 <p>Please review the “Minimum requirements for issues” section of |
| 287 contest’s <a class="reference internal" href="/native-client/community/sec
urity-contest/contest-terms.html"><em>Terms and Conditions</em></a>. You will fi
nd a |
| 288 list of all the information you will need to include in every |
| 289 submitted issue. Failure to provide this information might make the |
| 290 submitted issue invalid for the purposes of this contest.</p> |
| 291 </section><section id="how-do-i-contest-a-decision-that-a-bug-is-a-duplicate"> |
| 292 <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> |
| 293 <p>Please highlight this in our Google Group and a member of our team |
| 294 will get in touch with you.</p> |
| 295 </section><section id="why-is-the-native-client-team-updating-the-source-code-du
ring-the-contest"> |
| 296 <h2 id="why-is-the-native-client-team-updating-the-source-code-during-the-contes
t">Why is the Native Client team updating the source code during the contest?</h
2> |
| 297 <p>We are updating Native Client’s source code to fix bugs reported by |
| 298 contest participants or exploits identified by our team. Our goal is |
| 299 to protect contestants and other users of the Native Client software |
| 300 from exploits that could damage their system. In addition, by updating |
| 301 our builds, we will be providing you with more opportunities to find |
| 302 new security bugs. Finally, we believe this will make the contest more |
| 303 interesting by continuously raising the bar of bug finding.</p> |
| 304 </section><section id="i-forgot-to-include-something-in-the-summary-what-can-i-d
o"> |
| 305 <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> |
| 306 <p>If the contest has not ended, you may submit an updated summary. You |
| 307 may not submit an updated summary once the contest has ended.</p> |
| 308 </section><section id="someone-from-our-team-submitted-a-summary-on-behalf-of-ou
r-team-without-consulting-with-everyone-else-how-can-we-ensure-that-the-judges-w
ill-use-the-previous-summary-and-not-the-last-one"> |
| 309 <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-pre
vious-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 tha
t the judges will use the previous summary and not the last one?</h2> |
| 310 <p>If your team member submitted his / her version of the team’s summary |
| 311 before the end date of the contest, and if this is the last summary |
| 312 that was submitted from your team, then the Judges will disregard all |
| 313 previous versions of your summary and will only review this last |
| 314 one. If the contest has not ended, you may resubmit a previous summary |
| 315 to override the first.</p> |
| 316 </section><section id="will-you-be-evaluating-each-exploit-separately-for-every-
one-of-the-criteria"> |
| 317 <h2 id="will-you-be-evaluating-each-exploit-separately-for-every-one-of-the-crit
eria">Will you be evaluating each exploit separately for every one of the criter
ia?</h2> |
| 318 <p>We will use our criteria to evaluate submitted summaries, not |
| 319 individual exploits.</p> |
| 320 </section><section id="i-only-found-one-exploit-but-i-think-it-is-very-good-can-
i-still-win"> |
| 321 <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> |
| 322 <p>Yes. Quantity is only one of the criteria we use to evaluate submitted |
| 323 summaries.</p> |
| 324 </section><section id="how-are-you-going-to-pick-the-winners"> |
| 325 <h2 id="how-are-you-going-to-pick-the-winners">How are you going to pick the win
ners?</h2> |
| 326 <p>After the contest ends, all submitted Summaries will be judged by a |
| 327 panel of at least three judges. The judges will evaluate each Summary |
| 328 based on the following criteria: a) Quality (Severity, Scope, |
| 329 Reliability and Style) and b) Quantity. Each panel will evaluate a |
| 330 number of the submitted summaries and will select the highest ranking |
| 331 Summaries to move to the next level of judging. Those top Summaries |
| 332 will then be evaluated by all Judges using the same Criteria, and the |
| 333 top five Summaries will be selected as potential winners. For more |
| 334 information on the judging criteria and the judging process please |
| 335 review the relevant section of the <a class="reference internal" href="/native-c
lient/community/security-contest/contest-terms.html"><em>Terms and Conditions</e
m></a>.</p> |
| 336 </section><section id="when-and-how-are-we-going-to-find-out-the-results-of-the-
contest"> |
| 337 <h2 id="when-and-how-are-we-going-to-find-out-the-results-of-the-contest">When a
nd how are we going to find out the results of the contest?</h2> |
| 338 <p>We will contact all prospective winners at the email address provided |
| 339 to us at the registration process. You may request a list of winners |
| 340 after December 7th, 2009 by writing to: Native Client Security Contest |
| 341 Google Inc. 1600 Amphitheater Parkway Mountain View, CA 94043 USA</p> |
| 342 </section><section id="what-will-google-do-with-my-data"> |
| 343 <h2 id="what-will-google-do-with-my-data">What will Google do with my data?</h2> |
| 344 <p>The personal data you provided to Google during the Contest will be |
| 345 stored and processed in the US within the context of the Contest. We |
| 346 will maintain your data in the way described at the Google Privacy |
| 347 Policy found at <a class="reference external" href="http://www.google.com/privac
ypolicy.html">http://www.google.com/privacypolicy.html</a>. Google may |
| 348 use your data to verify your identity, postal address and telephone |
| 349 number in the event you qualify for a prize. You have a right to |
| 350 access and withdraw your personal data. To exercise this right, you |
| 351 may write to: Native Client Security Contest, Google Inc., 1600 |
| 352 Amphitheater Parkway, Mountain View, CA 94043, USA.</p> |
| 353 </section><section id="i-have-more-questions-where-can-i-get-a-response"> |
| 354 <h2 id="i-have-more-questions-where-can-i-get-a-response">I have more questions&
#8212;where can I get a response?</h2> |
| 355 <p>We recommend to ask any additional questions you might have in the |
| 356 Google Group. Members from our team will be monitoring the group and |
| 357 will respond to your question there, to benefit other contest |
| 358 participants.</p> |
| 359 </section><section id="i-like-this-project-are-you-hiring-people-to-work-on-it-f
ull-time"> |
| 360 <h2 id="i-like-this-project-are-you-hiring-people-to-work-on-it-full-time">I lik
e this project. Are you hiring people to work on it full time?</h2> |
| 361 <p>At Google we are always looking for great people. Please review our |
| 362 current openings at www.google.com/jobs.</p> |
| 363 </section><section id="how-can-i-get-involved-in-this-project-besides-the-contes
t"> |
| 364 <h2 id="how-can-i-get-involved-in-this-project-besides-the-contest">How can I ge
t involved in this project besides the contest?</h2> |
| 365 <p>Thank you for your interest in Native Client. You can help us by:</p> |
| 366 <ul class="small-gap"> |
| 367 <li>Identifying bugs</li> |
| 368 <li>Porting OS libraries</li> |
| 369 <li>Writing apps</li> |
| 370 </ul> |
| 371 <p>We would also like to see you participate in our discussion group.</p> |
| 372 </section><section id="why-is-my-country-province-excluded-from-the-contest"> |
| 373 <h2 id="why-is-my-country-province-excluded-from-the-contest">Why is my country/
province excluded from the contest?</h2> |
| 374 <p>While we seek to make this contest open worldwide, we cannot open it |
| 375 to residents of Cuba, Iran, Syria, North Korea, Sudan, or Myanmar |
| 376 (Burma) because of U.S. laws. In addition, the contest is not open to |
| 377 residents of Brazil, Italy, or Quebec because of local |
| 378 restrictions. For more information on eligibility, see the <a class="reference i
nternal" href="/native-client/community/security-contest/contest-terms.html"><em
>Terms |
| 379 and Conditions</em></a>.</p> |
| 380 </section></section> |
| 381 |
| 382 {{/partials.standard_nacl_article}} |
OLD | NEW |