The ICGA have created a page on Wikispaces https://icga.wikispaces.com/message/lis ... g+cheating
Here anyone can post ideas and proposed rule changes by clicking on the Discussion tab. You must 1st be a member of Wikispaces this takes about 11 seconds.
Only posts on this Wiki will be considered by the ICGA board.
Preventing cheating in future ICGA Events.
Moderator: Ras
-
Harvey Williamson
- Posts: 2030
- Joined: Sun May 25, 2008 11:12 pm
- Location: Whitchurch. Shropshire, UK.
- Full name: Harvey Williamson
-
Graham Banks
- Posts: 45951
- Joined: Sun Feb 26, 2006 10:52 am
- Location: Auckland, NZ
Re: Preventing cheating in future ICGA Events.
Don't run them, then nobody can be accused of cheating in them. 
gbanksnz at gmail.com
-
JuLieN
- Posts: 2949
- Joined: Mon May 05, 2008 12:16 pm
- Location: Bordeaux (France)
- Full name: Julien Marcel
Re: Preventing cheating in future ICGA Events.
My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
"The only good bug is a dead bug." (Don Dailey)
[Blog: http://tinyurl.com/predateur ] [Facebook: http://tinyurl.com/fbpredateur ] [MacEngines: http://tinyurl.com/macengines ]
[Blog: http://tinyurl.com/predateur ] [Facebook: http://tinyurl.com/fbpredateur ] [MacEngines: http://tinyurl.com/macengines ]
-
Sean Evans
- Posts: 1777
- Joined: Thu Jun 05, 2008 10:58 pm
- Location: Canada
Re: Preventing cheating in future ICGA Events.
Here is the best way to prevent cheating in the future of ICGA events:


-
Sarciness
- Posts: 43
- Joined: Tue Nov 23, 2010 4:22 pm
Re: Preventing cheating in future ICGA Events.
This did make me laugh! I was/am? a Rybka fan, but I feel very let down by Vas. If he doesn't respond to the charges I will not be purchasing any more Rybka products (should any even be released in the future!)Sean Evans wrote:Here is the best way to prevent cheating in the future of ICGA events:
-
BubbaTough
- Posts: 1154
- Joined: Fri Jun 23, 2006 5:18 am
Re: Preventing cheating in future ICGA Events.
This sounds extremely reasonable. Even when I was working on a private engine, and extremely reticent to share executables let alone source, I would have agreed to this.JuLieN wrote:My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
-Sam
-
bob
- Posts: 20943
- Joined: Mon Feb 27, 2006 7:30 pm
- Location: Birmingham, AL
Re: Preventing cheating in future ICGA Events.
What single person can you find to collect the sources that (a) is completely honest and (b) trusted to be honest by all participants, perticularly commercial ones that have much to lose if trade secrets are exposed?BubbaTough wrote:This sounds extremely reasonable. Even when I was working on a private engine, and extremely reticent to share executables let alone source, I would have agreed to this.JuLieN wrote:My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
-Sam
It sounds simple in theory, but the practical implementation is a _real_ bitch to do.
-
Edmund
- Posts: 670
- Joined: Mon Dec 03, 2007 3:01 pm
- Location: Barcelona, Spain
Re: Preventing cheating in future ICGA Events.
I find the phrasing of "require to authorize the consulting of the sources" way to vague. If I were to hand over sources of a commercial piece of software I would be more than interested in the process of "consulting" beforehand. Who gets to see the sources? Has the author any influence? I would propose as an optional alternative to the named procedure above, the author himself may chose 3 people well respected by the community, hand over the sources to them and have them vouch for security.JuLieN wrote:My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
-
Edmund
- Posts: 670
- Joined: Mon Dec 03, 2007 3:01 pm
- Location: Barcelona, Spain
Re: Preventing cheating in future ICGA Events.
It would be feasable that the programmer is given a tool for encrypting the source as well as 10 different keys one for each panel member. There would be ways to enable a decryption only with 7/10 keys available.bob wrote:What single person can you find to collect the sources that (a) is completely honest and (b) trusted to be honest by all participants, perticularly commercial ones that have much to lose if trade secrets are exposed?BubbaTough wrote:This sounds extremely reasonable. Even when I was working on a private engine, and extremely reticent to share executables let alone source, I would have agreed to this.JuLieN wrote:My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
-Sam
It sounds simple in theory, but the practical implementation is a _real_ bitch to do.
-
JuLieN
- Posts: 2949
- Joined: Mon May 05, 2008 12:16 pm
- Location: Bordeaux (France)
- Full name: Julien Marcel
Re: Preventing cheating in future ICGA Events.
You're right. But practical solutions, or beginning of practical solutions, come to mind quite fast. For instance, the contestant could submit an encrypted archive. If a problem occurs and the board votes a code examination, the programmer would be required the archive password. Failure to comply would probably rule against him.bob wrote:What single person can you find to collect the sources that (a) is completely honest and (b) trusted to be honest by all participants, perticularly commercial ones that have much to lose if trade secrets are exposed?BubbaTough wrote:This sounds extremely reasonable. Even when I was working on a private engine, and extremely reticent to share executables let alone source, I would have agreed to this.JuLieN wrote:My proposal:
"Any contestant shall provide the ICGA with the sources of his engine. These sources are to remain secret and undisclosed, except for one purpose:
- in case of doubt on the originality of the program, a majority of two thirds of the ICGA's board can vote to examine those sources to investigate the issue. The board shall be at least 10 persons large and the required number of members approving the examination of the sources will be rounded up to the immediate higher number (for instance, a positive vote of 7 out of 10 members are required to authorize the consulting of the sources). During such an investigation it will be the responsibility of the ICGA to prevent any leak or accidental disclosure of these sources, that will be kept secret but for the investigation panel. Only limited and illustrative parts of the sources can get published in the final public report."
-Sam
It sounds simple in theory, but the practical implementation is a _real_ bitch to do.
A problem that could occur is that the programmer would willingly provide a defective archive and, when confronted with this, answer that the ICGA damaged it. So when providing the archive the programmer would also have to provide a checksum, and would receive a "checksum confirmation" by the ICGA.
That way, the question of "who" would be less critical. Those sources archives should be stored by the ICGA, and the file access should be non-anonymous and logged.
There's always a solution, and I'm sure security professional would come with better ones.
"The only good bug is a dead bug." (Don Dailey)
[Blog: http://tinyurl.com/predateur ] [Facebook: http://tinyurl.com/fbpredateur ] [MacEngines: http://tinyurl.com/macengines ]
[Blog: http://tinyurl.com/predateur ] [Facebook: http://tinyurl.com/fbpredateur ] [MacEngines: http://tinyurl.com/macengines ]