On 6/11/10, David Anderson <[email protected]> wrote: > Josef W. Segur wrote: >> While researching a related issue, I noted that handle_results() in >> the trunk sched_result.cpp seems to be set to call got_bad_result() >> without checking if the exit code indicates the project has cancelled >> the task, etc. > > That's actually on purpose; consecutive_valid is used in > the cherry-picking defense mechanism, and bad guys can fake exit codes.
Isn't there a way to know if a result was aborted by the server without using any client-provided information? -- Nicolas _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
