http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=111933

2.5 time faster then 5870!

I think this is fake. Somebody modified the science app, to do only 1/4 of the work. I hope project admins will look into it.

---

I think this is fake. Somebody modified the science app, to do only 1/4 of the work. I hope project admins will look into it.

I think that someone compiled a single precision version of the cuda app. That happened here before and AFAIK the one got away with it too.

It would be best if the whole single precision code would be completely removed from the source code.

Boincstats -> http://de.boincstats.com/stats/host_graph.php?pr=milkyway&id=111933

As you can see, this has been going on for quite a while now...

Here's the user -> http://milkyway.cs.rpi.edu/milkyway/show_user.php?userid=61872 which by the way is the same person who messed with it some time ago in this thread -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1305#34439

I hope that someone will notify Travis and that actions will be taken to remove the host,user and all credits for both user and the team (SETI.Germany)....

---

Join Support science! Joinc Team BOINC United now!

Hmmm... Since no action was taken, it appears that there is nothing wrong with running SP apps. So, I think I'll install them also, as DP just waste electricity. I wonder, if many crunchers were to switch to SP apps, would the staff remain so indifferent?

---

Surely the simplest answer as has already been suggested, is to remove the single precision code. I can see no point in compounding the problem further.

---

Don't drink water, that's the stuff that rusts pipes

Hmmm... Since no action was taken, it appears that there is nothing wrong with running SP apps. So, I think I'll install them also, as DP just waste electricity. I wonder, if many crunchers were to switch to SP apps, would the staff remain so indifferent?

I wouldn't expect an immediate response. It seems to take awhile lately to hear anything back.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

That, and a required hash check for all apps. It shouldn't be hard to get a new hash for one of Cluster Physik's apps verified and accepted when they need to be updated, and this would at least make it more difficult to use unsanctioned code. Of course, hash checks -can- be spoofed, but hopefully no one is that dedicated to messing up the project.

That, and a required hash check for all apps. It shouldn't be hard to get a new hash for one of Cluster Physik's apps verified and accepted when they need to be updated, and this would at least make it more difficult to use unsanctioned code. Of course, hash checks -can- be spoofed, but hopefully no one is that dedicated to messing up the project.

Hash checks don't work here since he's using the anonymous platform. The only way i see to prevent this is to implement the double precision check for anonymous platform (planclass cuda23) too, like it's done for the stock cuda app.

---

Join Support science! Joinc Team BOINC United now!

That, and a required hash check for all apps. It shouldn't be hard to get a new hash for one of Cluster Physik's apps verified and accepted when they need to be updated, and this would at least make it more difficult to use unsanctioned code. Of course, hash checks -can- be spoofed, but hopefully no one is that dedicated to messing up the project.

Hash checks don't work here since he's using the anonymous platform. The only way i see to prevent this is to implement the double precision check for anonymous platform (planclass cuda23) too, like it's done for the stock cuda app.

Or going to initial replication of 2...
/me hides quickly

---

Hash checks don't work here since he's using the anonymous platform. The only way i see to prevent this is to implement the double precision check for anonymous platform (planclass cuda23) too, like it's done for the stock cuda app.

BOINC offers no mechanism for enforcing a hash check? i.e. through the results file? Using that check sounds like a good idea though, though probably easier to spoof.

Regarding these concerns, they have been escalated to Travis when the thread started and I just did so again.

---

Good, As a major Donor to the project, this deliberate sabotage of the project makes me VERY upset. The credits for this user need to be zeroed forthwith. Any further tampering may result in his team being punished as well(Need to be careful on this one).

But as someone with a weekly $100 power bill for this project, compiling unauthorised versions of the code, to increase ones credit, needs to treated very seriously.

Actually, I am a BIT angry as well, A final warning leading to banishment could well be appropriate as well.

Kind Regards

---

More than likely who ever it is will get a Polite Slap on the Wrist and asked if they would Please stop doing what their doing. Case in point the 40 Million Credits that a certain Team sucked up by running scripts a few weeks ago to abort the longer running Wu's ...

---

STE\/E

Poorboy---Not sure if you saw this on the Front Page but if it doesn't stop it's no more Mr Nice Admin:

Scripting to remove WUs from certain searches

I'd also like to put a note out there to people running scripts to cancel WUs from certain searches, asking you to stop. These can lead to some bad server problems where some WUs accumulate on the server because they're not being processed fast enough. We'll be taking some steps on the server end to stop this kind of activity, but until that gets finished I'd like to ask people to stop. If it continues I'll start banning or zeroing out offending users credit. --Travis 11 Mar 2010 2:53:25 UTC

---

I seen it and it just proves what I said, a slap on the wrist and a will you please stop, as usual though the perpetrators got to keep the goods ... :)

---

STE\/E

I seen it and it proves what I said, I slap on the wrist and please stop, as usual though the perpetrators got to keep the goods ... :)

Not with the information I just sent up to Travis...

---

So my Account is going to be Zeroed out then ... hahaha

---

STE\/E

It isn't too often that a lot has been carried through. I remember things from the past happening and most of what was done was a post on the front page. I don't remember that person(s) being punished. (could be wrong)

This went on way back when nano ran, users were turning bogus wus for huge credit and got zeroed out rather quickly.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Just received an email from Travis:

I'm actually in the middle of updating the validator; which should really stop the problem.

---

Just received an email from Travis:

I'm actually in the middle of updating the validator; which should really stop the problem.

I can assure you Burf, If this user is allowed to get away with this, the message being sent is "Try and rort the system, IF you get caught, nothing much will happen".

There needs be a consistent point deduction for this type of behaviour, otherwise you will continue to play "wack-a-mole".

I suggest a 10% deduction of total points, plus, email. A further 10%, of the remaining balance, should be deducted each week until the behavior stops.

If you want another NZD1,300.00 donation this year, please give this request serious consideration.

Kind Regards
David Glogau

---