Thursday Exercise 5 (optional)
From AIMSWiki
| Table of contents |
Overview
Think of a way to secure the program so that it only processes given results. Optionally implement it on client (Java) or server (Python) side.
Procedure
Server side
When you take a look inside work_generator there is a method add_sig, which currently doesn't do that much. Think about how you would implement a signing algorithm or think of another method to make it harder for someone to use your program for other causes than running BOINC. If you can, write an algorithm to secure the input file on the server side.
Client side
Of course, this method must be implemented on the client side as well. For instance in checkInputFile you could verify the use of STDSIM as well. Think of a method here as well, and write it if you can.
You have to be aware that the program is on the computer of the volunteer, so he can change anything that he wants (even, if he tries hard, the program). This is what is the big problem. We try to make the boundary as high as possible!
