Bingo ! While I am quite fluent in Win32 C++, I've never written any server-side code. So maybe not your first dollar, but you can get your first 10-cents from me !
Hashstamp-journaling is superior to code-signing for serious purposes, because as with Stuxnet, someone can steal a copy of a signing certificate and you might never know. With a hashstamp journal you can monitor the journal. Someone might silently steal your password, but of course you would see any entries they made *SO* non-edit, non-delete, but a "revocation stamp" would be a great feature saying exactly that happened. You would notice the hacked entries, FAR superior to code-signing.

deskpane.build.236 hashstamp below
This is somewhat off-topic. Do you know of any cheap hashstamp-servers ? By hashstamp-server I mean a place where you can make a datestamped, no-edit, no-delete entry containing say the hash of one of your builds. Not having found one of those, slashdot could make money, by offering the datestamped, no-edit, no-delete feature of discussion-comments FOR JOURNAL ENTRIES. A lite discussion in my Journal for slashdot user xpane, more discussion in the Journal for slashdot user hashstamp.
So anyway for today here is the hashstamp of a release-candidate build for my big idea. Thanks for tolerating this somewhat off-topic post, is there another way I could get the no-edit, no-delete feature without needlessly bothering anyone, perhaps even paying 10-cents for a hashstamp, I WOULD !?
file C:\zzzz\zzzzWcDemo\deskPane_win32_x64_2011_APR_11_00236.zip nbytes 0x4F543D 5198909 CRC32 f66b9662 MD5 3b0e7a6e545f7e7a8a34f6bfd152940a SHA-1 6806f4b125e950685a09314c2e56b361847150a5 SHA-256 95e04cb9a0d1bb953c9c6e68a642a76add61ebc51914a4cbbb95ecff1e08d15f