added suggestion about supporting alternate keys for same content

This commit is contained in:
Ilya_Shlyakhter 2018-10-29 19:43:25 +00:00 committed by admin
parent 9b268cdcc9
commit 50d99e19a3

View file

@ -0,0 +1,6 @@
Designate a metadata field, say alt_keys, to store alternate keys for the content designated by the key with the metadata.
Then, after initially adding a URL key, and after some time getting its content, a checksum-based key such as MD5 could be added as the URL key's metadata.
Then, without needing to migrate, the URL key could be treated like checksum-based keys, e.g. downloaded from untrusted remotes, fsck'ed, etc.
The problem with migrating keys is that a separate copy of the contents is stored in the annex under the old key; but it you force-drop that, symlinks in
older commits will become invalid. You could rewrite git history, but that brings its own problems.