Cryptographic hash computations for a revision range on the repository side
From: Thierry Moreau <thierry.moreau_at_connotech.com>
Date: Mon, 20 Jan 2014 23:11:40 -0500
Suppose someone becomes very paranoid that someone will surreptitiously
Digital signatures require public/private key protections, just shifting
So one solution is to hash (SHA-256) the range of revisions committed
At the end of the next on-duty period, the previous day hash value is
My questions are:
Do I need to hash more than the files db/revs/<n>/<nnn> and
Are these files end-of-line convention dependent? (I guess yes)
Any other reason why the db/revprops/<n>/<nnn> contents would
I am using version 1.7.
If any interest in this concept, let me know.
Thanks in advance,
-- - Thierry MoreauReceived on 2014-01-21 05:56:41 CET
This is an archived mail posted to the Subversion Users mailing list.