Author: kotkov
Date: Wed Mar 22 15:28:17 2023
New Revision: 1908641

URL: http://svn.apache.org/viewvc?rev=1908641&view=rev
Log:
On the 'pristine-checksum-salt' branch: Update BRANCH-README.

* BRANCH-README: Tweak the section about pristine checksum kinds.
  Add a section about using the dynamically salted SHA-1.

Modified:
    subversion/branches/pristine-checksum-salt/BRANCH-README

Modified: subversion/branches/pristine-checksum-salt/BRANCH-README
URL: 
http://svn.apache.org/viewvc/subversion/branches/pristine-checksum-salt/BRANCH-README?rev=1908641&r1=1908640&r2=1908641&view=diff
==============================================================================
--- subversion/branches/pristine-checksum-salt/BRANCH-README (original)
+++ subversion/branches/pristine-checksum-salt/BRANCH-README Wed Mar 22 
15:28:17 2023
@@ -2,7 +2,7 @@ Configurable pristine checksum kind in a
 -----------------------------------------------------
 
 The implementation on the branch allows creating working copies that use a
-checksum kind other than SHA-1.
+checksum kind other than plain SHA-1.
 
 The checksum kind is persisted in the settings table.  Upgraded working copies
 of the older formats will have SHA-1 recorded as their pristine checksum kind
@@ -10,9 +10,8 @@ and will continue to use it for compatib
 of the latest format (with --compatible-version=1.15 or --store-pristine=no),
 as currently implemented, will use the new pristine checksum kind.
 
-Currently, as a proof-of-concept, the branch uses salted SHA-1 as the new
-pristine checksum kind.  For the production-ready state, we could support
-using multiple new checksum types such as SHA-256.  That could be useful
-for future compatibility, because if we encounter any issues with one
-checksum kind, we could then switch to a different kind without having
-to change the working copy format.
+Dynamically salted SHA-1 checksums
+----------------------------------
+
+The implementation on the branch uses a dynamically salted SHA-1 checksum kind.
+The dynamic salt is generated during the creation of a wc.db.


Reply via email to