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

Side by Side Diff: native_client_sdk/src/doc/community/security-contest/contest-terms.rst

Issue 476793002: Per P0 reqs add launch pts + make download obvious. Also misc cpy edits. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: CL synced with master. 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
« no previous file with comments | « native_client_sdk/src/doc/c-api.rst ('k') | native_client_sdk/src/doc/cpp-api.rst » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 .. _contest_terms: 1 .. _contest_terms:
2 2
3 ##################################### 3 #####################################
4 Security Contest Terms and Conditions 4 Security Contest Terms and Conditions
5 ##################################### 5 #####################################
6 6
7 .. contents:: 7 .. contents::
8 :local: 8 :local:
9 :backlinks: none 9 :backlinks: none
10 :depth: 2 10 :depth: 2
(...skipping 47 matching lines...) Expand 10 before | Expand all | Expand 10 after
58 The Contest is organized by Google and is designed to motivate the 58 The Contest is organized by Google and is designed to motivate the
59 developer community to identify and report security Exploits (as 59 developer community to identify and report security Exploits (as
60 defined below) on Google’s Native Client software and reward those 60 defined below) on Google’s Native Client software and reward those
61 developers who identify one or more security Exploits that are 61 developers who identify one or more security Exploits that are
62 evaluated as a winning exploit by the Judges. 62 evaluated as a winning exploit by the Judges.
63 63
64 Once a Participant has registered for the Contest, the Participant 64 Once a Participant has registered for the Contest, the Participant
65 will be asked to identify security Exploits in Google’s Native 65 will be asked to identify security Exploits in Google’s Native
66 Client Software and enter those Exploits on Google’s `Native Client 66 Client Software and enter those Exploits on Google’s `Native Client
67 Issue Tracker <http://code.google.com/p/nativeclient/issues/list>`_ 67 Issue Tracker <http://code.google.com/p/nativeclient/issues/list>`_
68 web site using the "Security Contest Template." At this point, the 68 website using the "Security Contest Template." At this point, the
69 Exploit will become an Issue and will no longer be able to be 69 Exploit will become an Issue and will no longer be able to be
70 identified by another Participant. Google will then verify that the 70 identified by another Participant. Google will then verify that the
71 Issue is reproducible. If so, that Issue will become a Verified 71 Issue is reproducible. If so, that Issue will become a Verified
72 Issue. Finally, the Participant will submit a Summary of up to his 72 Issue. Finally, the Participant will submit a Summary of up to his
73 or her top ten best Issues that were submitted on the `Native 73 or her top ten best Issues that were submitted on the `Native
74 Client Issue Tracker 74 Client Issue Tracker
75 <http://code.google.com/p/nativeclient/issues/list>`_. Since it is 75 <http://code.google.com/p/nativeclient/issues/list>`_. Since it is
76 possible that an Issue may not be verified until after the Contest 76 possible that an Issue may not be verified until after the Contest
77 End Date, if a Participant includes such an Issue in their Summary 77 End Date, if a Participant includes such an Issue in their Summary
78 and such Issue is not ultimately verified, then that Issue will not 78 and such Issue is not ultimately verified, then that Issue will not
(...skipping 686 matching lines...) Expand 10 before | Expand all | Expand 10 after
765 threatens or harasses any other Participants, Google, or the 765 threatens or harasses any other Participants, Google, or the
766 Judges. Google further reserves the right to disqualify any 766 Judges. Google further reserves the right to disqualify any
767 Issue that it believes in its sole and unfettered discretion 767 Issue that it believes in its sole and unfettered discretion
768 infringes upon or violates the rights of any third party, 768 infringes upon or violates the rights of any third party,
769 otherwise does not comply with these Terms, or violates U.S. or 769 otherwise does not comply with these Terms, or violates U.S. or
770 applicable local law in Participant's country of residence. 770 applicable local law in Participant's country of residence.
771 771
772 Google further reserves the right to disqualify any Participant 772 Google further reserves the right to disqualify any Participant
773 who tampers with the submission process or any other part of the 773 who tampers with the submission process or any other part of the
774 Contest. Any attempt by a Participant to deliberately damage any 774 Contest. Any attempt by a Participant to deliberately damage any
775 web site or undermine the legitimate operation of the Contest is 775 website or undermine the legitimate operation of the Contest is
776 a violation of criminal and civil laws and should such an 776 a violation of criminal and civil laws and should such an
777 attempt be made, Google reserves the right to seek damages from 777 attempt be made, Google reserves the right to seek damages from
778 any such Participant to the fullest extent of the applicable 778 any such Participant to the fullest extent of the applicable
779 law. 779 law.
780 780
781 #. Internet Disclaimer. Google is not responsible for any 781 #. Internet Disclaimer. Google is not responsible for any
782 malfunction of the entire Contest, the web site displaying the 782 malfunction of the entire Contest, the website displaying the
783 Contest terms and entry information, or any late, lost, damaged, 783 Contest terms and entry information, or any late, lost, damaged,
784 misdirected, incomplete, illegible, undeliverable, or destroyed 784 misdirected, incomplete, illegible, undeliverable, or destroyed
785 Exploits, Issues or Summaries due to system errors, failed, 785 Exploits, Issues or Summaries due to system errors, failed,
786 incomplete or garbled computer or other telecommunication 786 incomplete or garbled computer or other telecommunication
787 transmission malfunctions, hardware or software failures of any 787 transmission malfunctions, hardware or software failures of any
788 kind, lost or unavailable network connections, typographical or 788 kind, lost or unavailable network connections, typographical or
789 system/human errors and failures, technical malfunction(s) of 789 system/human errors and failures, technical malfunction(s) of
790 any telephone network or lines, cable connections, satellite 790 any telephone network or lines, cable connections, satellite
791 transmissions, servers or providers, or computer equipment, 791 transmissions, servers or providers, or computer equipment,
792 traffic congestion on the Internet or at the web site displaying 792 traffic congestion on the Internet or at the website displaying
793 the Contest or any combination thereof, including other 793 the Contest or any combination thereof, including other
794 telecommunication, cable, digital or satellite malfunctions 794 telecommunication, cable, digital or satellite malfunctions
795 which may limit an entrant’s ability to participate. Google is 795 which may limit an entrant’s ability to participate. Google is
796 not responsible for availability of the `Native Client Issue 796 not responsible for availability of the `Native Client Issue
797 Tracker <http://code.google.com/p/nativeclient/issues/list>`_ 797 Tracker <http://code.google.com/p/nativeclient/issues/list>`_
798 from your preferred point of Internet access. In the event of a 798 from your preferred point of Internet access. In the event of a
799 technical disruption, Google may, in its sole discretion, extend 799 technical disruption, Google may, in its sole discretion, extend
800 the Contest End Date for a reasonable period. Google will 800 the Contest End Date for a reasonable period. Google will
801 attempt to notify Participants of any such extension by email at 801 attempt to notify Participants of any such extension by email at
802 the email address in the registration information, but shall 802 the email address in the registration information, but shall
(...skipping 174 matching lines...) Expand 10 before | Expand all | Expand 10 after
977 You may request a list of winners after December 7th, 2009 by 977 You may request a list of winners after December 7th, 2009 by
978 writing to: 978 writing to:
979 979
980 | Native Client Security Contest 980 | Native Client Security Contest
981 | Google Inc. 981 | Google Inc.
982 | 1600 Amphitheater Parkway 982 | 1600 Amphitheater Parkway
983 | Mountain View, CA 94043 983 | Mountain View, CA 94043
984 | USA 984 | USA
985 985
986 (Residents of Vermont need not supply postage). 986 (Residents of Vermont need not supply postage).
OLDNEW
« no previous file with comments | « native_client_sdk/src/doc/c-api.rst ('k') | native_client_sdk/src/doc/cpp-api.rst » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698