mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

updates

Browse source 
Note that I tried an evil remote that lists ImportLocations with
../../../ in them and indeed this resulted in git blowing up and the
import failing, and not writing outside the repo.
This commit is contained in:
Joey Hess 2019-03-06 17:07:29 -04:00
parent 8e9713b769
commit dec30d2b14
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 17 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/todo/import_tree.mdwn
View file

@ -10,13 +10,8 @@ this.
## implementation notes
* After adding a new file with different content to local and remote, then
importing and resolving the merge conflict, exporting the resolution
fails. It seems it's lost the old CID for the remote's content.
Hmm, can't reproduce that now, I may have been confused?
* getknowncids should run "updateexportdb exportdb exportdbv",
* getknowncids should run "updateexportdb exportdb exportdbv"
to make sure it sees the most current data,
but that leads to a STM deadlock for some reason?
* Need to support annex-tracking-branch configuration, which documentation
@ -30,10 +25,19 @@ this.
It will only need to be updated when listContents returns a
ContentIdentifier that is not already known in the database.
How to do the update: Stash the ref of the last git-annex branch it's
updated from in the database. Diff between that ref and the current
git-annex branch. For each file in the diff that's a .cid file, read
the file from the branch, and store into the database.
Update the stashed ref.
* When on an adjusted unlocked branch, need to import the files unlocked.
Also, the tracking branch code needs to know about such branches,
currently it will generate the wrong tracking branch.
The test case for `export_import` currently has a line commented out
that fails on adjusted unlocked branches.
* What if the remote lists importable filenames that are absolute paths,
or contain a "../" attack? Does git already guard against merging such
trees?