Restore a symlink changes target attributes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi,
Using --file-to-restore option on a symlink, I've found that it changes the mod (644->777) of the target file.
Technical infos :
duplicity 0.6.17
Python 2.6.5
Ubuntu 10.04.3
Target FileSystem : ext4
Steps to reproduce it :
$ mkdir -p ~/tmp/duplicity
$ cd ~/tmp/duplicity/
$ touch ~/tmp/fooo
$ ln -s ~/tmp/fooo fooo
$ ls -l ~/tmp/fooo fooo
lrwxrwxrwx 1 bancal bancal 21 2012-02-10 14:33 fooo -> /home/bancal/
-rw-r--r-- 1 bancal bancal 0 2012-02-10 14:32 /home/bancal/
$ duplicity --no-encryption /home/bancal/
$ rm fooo
$ duplicity --no-encryption --file-to-restore fooo file://
$ ls -l /home/bancal/
lrwxrwxrwx 1 bancal bancal 21 2012-02-10 14:36 fooo -> /home/bancal/
-rwxrwxrwx 1 bancal bancal 0 2012-02-10 14:33 /home/bancal/
# Note that original file's mod has changed to 777!!! (even if it is outside the scope of the backup!)
Changed in duplicity: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 0.8.21 |
Changed in duplicity: | |
milestone: | 0.8.21 → 0.8.22 |
Changed in duplicity: | |
status: | Confirmed → Incomplete |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Hi
I stumbled upon this issue recently and found this old bug report. I believe this is a security issue.
Are the developers still working on bug reports here at launchpad, or should we reopen this over at https:/ /gitlab. com/duplicity/ duplicity ?