• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

proving an executable has not changed

 
steve kilgore
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Several teams are submitting prototypes for review by a certain date. These will be viewed on their own servers. So I am looking for a utility that will prove that the prototype has not been changed since the deadline date. thanks.
 
Akhilesh Trivedi
Ranch Hand
Posts: 1599
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If I am not understanding it wrong, you have some competition running up somewhere and accepting something.

These (submission)will be viewed on their own(people's) servers.


I guess here is the trouble. Anyways be honest with the deadline date on your side too. Do not pull them from their servers after deadline date. [ ]
 
Michael Ernest
High Plains Drifter
Sheriff
Posts: 7292
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you have a file system mechanism in place that allows snapshots, problem solved. If not, you could taking a checksum or hash of the file at the deadline -- a fingerprint, in effect -- and then compare it to the file at the point of review.

On the whole, however, I don't think one can examine a file first at point C in time and prove it has not changed since point B in time. Depending on the file system and the ignorance of the local admin or programmer, you could at best infer, for many cases if not most, that the file had or hadn't been changed.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic