computer-go: prevent cheating

[Sai To Wang <swang@xxxxxxxxxx>]

>From richard@xxxxxxxxxxxxxxxxx  Thu Oct 14 16:02:00 1999
Received: from mailserver.shd.gov.co ([216.72.4.140])
	by darkwing.uoregon.edu (8.9.3/8.9.3) with ESMTP id QAA25178
	for <computer-go@xxxxxxxxxxxxxxxxx>; Thu, 14 Oct 1999 16:01:54 -0700 (PDT)
Received: by MAILSERVER with Internet Mail Service (5.5.2448.0)
	id <TYLN44N2>; Thu, 14 Oct 1999 17:17:35 -0500
Message-ID: <F106E8774A54D311ADA800805F91A3B4168D09@P800>
From: Sai To Wang <swang@xxxxxxxxxxxxxxxxx>
To: computer-go@xxxxxxxxxxxxxxxxx
Subject: prevent cheating
Date: Thu, 14 Oct 1999 17:17:35 -0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"


There is a way to prevent cheating, if we have the following rules:

1)	A official standard of protocol over internet.
2)	A official standard GUI.
3)	A official standard for inicial parameters. (.INI file)
4)	Only use a unique and proved official pseudo-random generator.
	All random seed will be stated in the inicial parameters file.
	(So the program will behave exactly the same when had the same
input)

5)	A official standard for running platform.

6)	Before the tournament, there is an official deadline for all the
	competitor to digitally sign and timestamp there package.
	the package include all the files that will be use in runtime
including 	the .ini file and hardware info.
	No change can be done after the deadline.

7)	The digital sign and timestamp infomation will be send to the
organizer
	when a official game will start (part of the protocol).
	All the play and the result (digitally signed and timestamped) is
also
	send to the organizer.

8)	In case of any sign of flaud or in the finals rounds, those games
can be 
	easly verified, just re running the game in the organizer place,
	using copy of the package of both player, since the organizer had
	both digital sign and timestamp there will be no flaud.