Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1229)

Side by Side Diff: native_client_sdk/doc_generated/community/security-contest/contest-faq.html

Issue 438403003: [NaCl SDK Docs] Only generate one top-level <section> element. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 {{+bindTo:partials.standard_nacl_article}} 1 {{+bindTo:partials.standard_nacl_article}}
2 2
3 <section id="security-contest-faq"> 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> 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"> 5 <aside class="caution">
6 The Native Client Security Contest has ended&#8212;check out the 6 The Native Client Security Contest has ended&#8212;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 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 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 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>. 10 participating in the <a class="reference external" href="http://groups.google.co m/group/native-client-discuss">Native Client discussion group</a>.
(...skipping 41 matching lines...) Expand 10 before | Expand all | Expand 10 after
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> 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> 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> 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> 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&#8212;where can I get a response?</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&#8212;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> 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> 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> 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> 60 </ul>
61 61
62 </div><section id="what-is-this-contest-about"> 62 </div><h2 id="what-is-this-contest-about">What is this contest about?</h2>
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 63 <p>We launched this contest in order to help make Native Client more
65 secure. We invite participants to discover security bugs in our 64 secure. We invite participants to discover security bugs in our
66 technology in order to compete to win cash prizes.</p> 65 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> 66 <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> 67 <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> 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>
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> 69 <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 70 <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> 71 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> 72 <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 73 <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 74 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 &lt;contest-terms&gt;`. Once everyone 75 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 &lt;contest-terms&gt;`. 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 76 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 77 Client issue tracker. You should not submit any bugs as part of your
82 contest entries until everyone on your team has accepted the 78 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 79 <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> 80 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> 81 <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 82 <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 83 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 84 the latest build of Native Client, attack it, and identify security
90 exploits. Submit these bugs through our Native Client Issue Tracker as 85 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 86 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 87 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 88 contest, you will need to submit a summary with the top 10 exploits
94 you identified. Our judges will review submitted summaries and will 89 you identified. Our judges will review submitted summaries and will
95 select the top 5 contestants.</p> 90 select the top 5 contestants.</p>
96 </section><section id="how-many-prizes-are-there-what-are-the-prizes"> 91 <h2 id="how-many-prizes-are-there-what-are-the-prizes"><span id="contest-faq-pri zes"></span>How many prizes are there? What are the prizes?</h2>
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 92 <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 93 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> 94 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> 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>
103 <p>You can sign up as a team. There is no limit to how many people can 96 <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 97 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 98 of your team small so as to be able to better coordinate during the
106 contest.</p> 99 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> 100 <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, 101 <p>To participate, you will need to test the Native Client builds,
110 identify security exploits which affect the current Native Client 102 identify security exploits which affect the current Native Client
111 build at the time of submission and report them to our team. Our 103 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 104 judges will review your entry. If you are one of the top five
113 participants selected by the judges and satisfy the requirements for 105 participants selected by the judges and satisfy the requirements for
114 eligibility, then you will win a cash prize. For more information on 106 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 107 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> 108 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> 109 <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 110 <p>Google has recruited a group of distinguished security experts to
120 serve as judges for this contest:</p> 111 serve as judges for this contest:</p>
121 <ul class="small-gap"> 112 <ul class="small-gap">
122 <li>Edward Felten — jury chair (Princeton)</li> 113 <li>Edward Felten — jury chair (Princeton)</li>
123 <li>Alex Halderman (Michigan)</li> 114 <li>Alex Halderman (Michigan)</li>
124 <li>Brad Karp (University College London)</li> 115 <li>Brad Karp (University College London)</li>
125 <li>Greg Morrisett (Harvard)</li> 116 <li>Greg Morrisett (Harvard)</li>
126 <li>Niels Provos (Google)</li> 117 <li>Niels Provos (Google)</li>
127 <li>Stefan Savage (UCSD)</li> 118 <li>Stefan Savage (UCSD)</li>
128 <li>Dan Wallach (Rice)</li> 119 <li>Dan Wallach (Rice)</li>
129 <li>Bennet Yee (Google)</li> 120 <li>Bennet Yee (Google)</li>
130 <li>Nickolai Zeldovich (MIT)</li> 121 <li>Nickolai Zeldovich (MIT)</li>
131 </ul> 122 </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 123 <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> 124 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> 125 <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 126 <p>You can start submitting issues after you and your team members (if
137 any) have completed the registration process and accepted the 127 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> 128 <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&#8212;what can I do?</h2> 129 <h2 id="registration-does-not-work-for-me-what-can-i-do">Registration does not w ork for me&#8212;what can I do?</h2>
141 <p>We recommend that you post this problem at the Google Group. Once you 130 <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 131 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 132 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> 133 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> 134 <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 135 <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&#37;&#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>goog le<span>&#46;</span>com</a>) and indicate 136 (it should be sent to <a class="reference external" href="mailto:nacl-security-c ontest&#37;&#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>goog le<span>&#46;</span>com</a>) and indicate
149 the changes you&#8217;d like to make. Please note that neither the team name 137 the changes you&#8217;d like to make. Please note that neither the team name
150 nor team membership can be changed once all members have accepted the 138 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> 139 <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> 140 <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 141 <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 142 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 143 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 144 into account unless you (and all your team members) have completed the
158 registration process prior to submitting any bugs.</p> 145 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> 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 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&#8217;s composition, or to update the contact 147 <p>To make edits to your team&#8217;s composition, or to update the contact
162 information of a team member, you will need to reply to one of the 148 information of a team member, you will need to reply to one of the
163 registration emails you received (it should be sent to 149 registration emails you received (it should be sent to
164 <a class="reference external" href="mailto:nacl-security-contest&#37;&#52;&#48;g oogle&#46;com">nacl-security-contest<span>&#64;</span>google<span>&#46;</span>co m</a>) and indicate the changes you&#8217;d like 150 <a class="reference external" href="mailto:nacl-security-contest&#37;&#52;&#48;g oogle&#46;com">nacl-security-contest<span>&#64;</span>google<span>&#46;</span>co m</a>) and indicate the changes you&#8217;d like
165 to make. Please note that this will mean that your team members will 151 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&#8217;s 152 receive an email notifying them of the changes in the team&#8217;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 153 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 154 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 155 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> 156 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> 157 <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 158 <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 159 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> 160 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> 161 <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 162 <p>Google will not be responsible for the division of any prize money
179 between members of a potential winning team. Instead Google will 163 between members of a potential winning team. Instead Google will
180 deliver the prize to one member indicated by the team. The team is 164 deliver the prize to one member indicated by the team. The team is
181 solely responsible for managing the logistics of distributing the 165 solely responsible for managing the logistics of distributing the
182 prize among team members. This is why Google asks all participating 166 prize among team members. This is why Google asks all participating
183 teams to identify a prize recipient.</p> 167 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> 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>
186 <p>To make edits to the prize recipient before all team members have 169 <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 170 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 171 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&#37;&#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>google<s pan>&#46;</span>com</a>) and indicate the 172 should be sent to <a class="reference external" href="mailto:nacl-security-conte st&#37;&#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>google<s pan>&#46;</span>com</a>) and indicate the
190 changes you&#8217;d like to make. Please note that this will mean that your 173 changes you&#8217;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 174 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 175 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 176 <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 177 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 178 <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> 179 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> 180 <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 181 <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 182 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 183 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 184 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 185 legal information that Google will need to comply with US and
204 international legal and tax regulations.</p> 186 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> 187 <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> 188 <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> 189 <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> 190 <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> 191 <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 192 <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 193 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 194 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 195 Native Client Security Contest. If you want to participate in this
217 person&#8217;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 196 person&#8217;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 197 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 198 member of a different team, then you can remove yourself from the list
220 of team members of that particular team.</p> 199 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> 200 <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&#8217;s original team (including 201 <p>If everyone in your potential teammate&#8217;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 202 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 203 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 204 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 205 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&#37; &#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>google<span>&#4 6;</span>com</a>) and indicate the changes 206 be sent to <a class="reference external" href="mailto:nacl-security-contest&#37; &#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>google<span>&#4 6;</span>com</a>) and indicate the changes
229 to be made. Please note that this will mean that his/her team members 207 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&#8217;s 208 will receive an email notifying them of the changes in the team&#8217;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 209 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 210 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 211 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> 212 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> 213 <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&#8217;t worry, just send us an email at <a class="reference external" hre f="mailto:nacl-security-contest&#37;&#52;&#48;google&#46;com">nacl-security-cont est<span>&#64;</span>google<span>&#46;</span>com</a> 214 <p>Don&#8217;t worry, just send us an email at <a class="reference external" hre f="mailto:nacl-security-contest&#37;&#52;&#48;google&#46;com">nacl-security-cont est<span>&#64;</span>google<span>&#46;</span>com</a>
238 and we will send you the link you need.</p> 215 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 > 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 >
241 <p>Your team is now considered to be invalid. If this rejection happened 217 <p>Your team is now considered to be invalid. If this rejection happened
242 by accident, please restart the registration process. If it was 218 by accident, please restart the registration process. If it was
243 deliberate then create a new team with teammates who are willing to 219 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 220 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 221 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 222 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> 223 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> 224 <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 225 <p>The judges will evaluate each Summary based on the following
251 criteria: a) Quality (Severity, Scope, Reliability and Style) and b) 226 criteria: a) Quality (Severity, Scope, Reliability and Style) and b)
252 Quantity. Please review the judging criteria in the contest 227 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> 228 <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> 229 <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> 230 <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> 231 <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 232 <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 233 Client issue tracker. A summary can include multiple issues but not
261 more than 10.</p> 234 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> 235 <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 236 <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 237 members (if any) submitted to the Native Client Issue tracker. We
266 recommend that you carefully review the judging criteria in the 238 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 239 <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 240 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 241 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 242 have been marked as duplicates or unverifiable, as these will not be
271 taken into account by our judges.</p> 243 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> 244 <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&#8217; time wisely. Rather than 245 <p>We want to make sure that we use our judges&#8217; time wisely. Rather than
275 having them review hundreds of similar or small scale bugs, sometimes 246 having them review hundreds of similar or small scale bugs, sometimes
276 identified with the same automatic process, we are limiting the number 247 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> 248 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&#8212;will this count against me in the judging proce ss?</h2> 249 <h2 id="my-english-is-not-great-will-this-count-against-me-in-the-judging-proces s">My English is not great&#8212;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 250 <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 251 incomprehensible by the judges will not be reviewed. We do not plan to
282 penalize summaries for spelling or grammar mistakes, but please make 252 penalize summaries for spelling or grammar mistakes, but please make
283 your descriptions as clear as possible.</p> 253 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> 254 <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 &#8220;Minimum requirements for issues&#8221; section of 255 <p>Please review the &#8220;Minimum requirements for issues&#8221; section of
287 contest&#8217;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 256 contest&#8217;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 257 list of all the information you will need to include in every
289 submitted issue. Failure to provide this information might make the 258 submitted issue. Failure to provide this information might make the
290 submitted issue invalid for the purposes of this contest.</p> 259 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> 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>
293 <p>Please highlight this in our Google Group and a member of our team 261 <p>Please highlight this in our Google Group and a member of our team
294 will get in touch with you.</p> 262 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> 263 <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&#8217;s source code to fix bugs reported by 264 <p>We are updating Native Client&#8217;s source code to fix bugs reported by
298 contest participants or exploits identified by our team. Our goal is 265 contest participants or exploits identified by our team. Our goal is
299 to protect contestants and other users of the Native Client software 266 to protect contestants and other users of the Native Client software
300 from exploits that could damage their system. In addition, by updating 267 from exploits that could damage their system. In addition, by updating
301 our builds, we will be providing you with more opportunities to find 268 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 269 new security bugs. Finally, we believe this will make the contest more
303 interesting by continuously raising the bar of bug finding.</p> 270 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&#8212;what can I do?</h2> 271 <h2 id="i-forgot-to-include-something-in-the-summary-what-can-i-do">I forgot to include something in the summary&#8212;what can I do?</h2>
306 <p>If the contest has not ended, you may submit an updated summary. You 272 <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> 273 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> 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-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&#8217;s summary 275 <p>If your team member submitted his / her version of the team&#8217;s summary
311 before the end date of the contest, and if this is the last summary 276 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 277 that was submitted from your team, then the Judges will disregard all
313 previous versions of your summary and will only review this last 278 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 279 one. If the contest has not ended, you may resubmit a previous summary
315 to override the first.</p> 280 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> 281 <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 282 <p>We will use our criteria to evaluate submitted summaries, not
319 individual exploits.</p> 283 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> 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>
322 <p>Yes. Quantity is only one of the criteria we use to evaluate submitted 285 <p>Yes. Quantity is only one of the criteria we use to evaluate submitted
323 summaries.</p> 286 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> 287 <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 288 <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 289 panel of at least three judges. The judges will evaluate each Summary
328 based on the following criteria: a) Quality (Severity, Scope, 290 based on the following criteria: a) Quality (Severity, Scope,
329 Reliability and Style) and b) Quantity. Each panel will evaluate a 291 Reliability and Style) and b) Quantity. Each panel will evaluate a
330 number of the submitted summaries and will select the highest ranking 292 number of the submitted summaries and will select the highest ranking
331 Summaries to move to the next level of judging. Those top Summaries 293 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 294 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 295 top five Summaries will be selected as potential winners. For more
334 information on the judging criteria and the judging process please 296 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> 297 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> 298 <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 299 <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 300 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 301 after December 7th, 2009 by writing to: Native Client Security Contest
341 Google Inc. 1600 Amphitheater Parkway Mountain View, CA 94043 USA</p> 302 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> 303 <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 304 <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 305 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 306 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 307 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 308 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 309 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 310 access and withdraw your personal data. To exercise this right, you
351 may write to: Native Client Security Contest, Google Inc., 1600 311 may write to: Native Client Security Contest, Google Inc., 1600
352 Amphitheater Parkway, Mountain View, CA 94043, USA.</p> 312 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> 313 <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 314 <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 315 Google Group. Members from our team will be monitoring the group and
357 will respond to your question there, to benefit other contest 316 will respond to your question there, to benefit other contest
358 participants.</p> 317 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> 318 <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 319 <p>At Google we are always looking for great people. Please review our
362 current openings at www.google.com/jobs.</p> 320 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> 321 <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> 322 <p>Thank you for your interest in Native Client. You can help us by:</p>
366 <ul class="small-gap"> 323 <ul class="small-gap">
367 <li>Identifying bugs</li> 324 <li>Identifying bugs</li>
368 <li>Porting OS libraries</li> 325 <li>Porting OS libraries</li>
369 <li>Writing apps</li> 326 <li>Writing apps</li>
370 </ul> 327 </ul>
371 <p>We would also like to see you participate in our discussion group.</p> 328 <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> 329 <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 330 <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 331 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 332 (Burma) because of U.S. laws. In addition, the contest is not open to
377 residents of Brazil, Italy, or Quebec because of local 333 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 334 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> 335 and Conditions</em></a>.</p>
380 </section></section> 336 </section>
381 337
382 {{/partials.standard_nacl_article}} 338 {{/partials.standard_nacl_article}}
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698