I would not chose way of development where "good guys" will suffer from features aimed to constrain "bad guys". Consider M$ way - their activation mechanism and long serial numbers to enter by hands (if you want it to do legal). And what? No "pirate" Windows versions? Every, including latest Windows7 version was successfully cracked. Any available today activation mechanism successfully circumvented. And it's not question of years, it's a question of few weeks from time when binaries become available. What I trying to say: if someone will have strong intention to abort result - [s]he will found a way. If you will push harder enough - you will end with expected system level stability ~ stability of dedicated cluster hardware...
----- Original Message ----- From: "David Anderson" <[email protected]> To: "Josef W. Segur" <[email protected]> Cc: <[email protected]> Sent: Friday, June 11, 2010 8:09 AM Subject: Re: [boinc_dev] consecutive_valid and server abort > 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. > > -- David > _______________________________________________ > 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. > _______________________________________________ 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.
