File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Programming Diversions and the fly likes proving an executable has not changed Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Other » Programming Diversions
Bookmark "proving an executable has not changed" Watch "proving an executable has not changed" New topic

proving an executable has not changed

steve kilgore

Joined: Jul 21, 2008
Posts: 2
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

Joined: Jun 22, 2005
Posts: 1599
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. [ ]

Keep Smiling Always — My life is smoother when running silent. -paul
[FAQs] [Certification Guides] [The Linux Documentation Project]
Michael Ernest
High Plains Drifter

Joined: Oct 25, 2000
Posts: 7292

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.

Make visible what, without you, might perhaps never have been seen.
- Robert Bresson
I agree. Here's the link:
subject: proving an executable has not changed
It's not a secret anymore!