Closed philipdexter closed 11 years ago
One downside to the current system is that if a student submits more than once , the salt will be the same for both. Other than that I think the current solution is strong. Ideas? The downside of using the timestamp along with the hash is that it would be near impossible for us to check their hash without knowing exactly when they submitted. Similarly, the downside of using their submission content is that we would need the actual submission to verify their hash.
You could check how many times they've submitted for that assignment, and then add the count to the hashed string. I can't look it up now (or the submission directory hierarchy), but you should probably be able to glob by username and assignment and then count the existing dirs. Then construct the hash from salt + username + assignment + count
.
A verification system will be most beneficial when we get students who claim that they submitted a project when one is not present for them.
One way to do this would be to give each project submission a unique id - when a student claims that they submitted a project we need only to ask them the id of the submission. If they are telling the truth then no other submission will have that id.
Another way might involve sending the students an email confirmation.