You have been subscribed to a public bug by Duncan Lithgow (duncan-lithgow):
Binary package hint: trash-cli
Version: 0.10.r55-0ubuntu1
I was experimenting with the trash-removal aspect of the package and
found what could be viewed as a serious issue.
emtpy-trash's only argument is number-of-days-since-deletion. There is
no way to otherwise limit what it removes, In some circumstances this
could be far too broad.
Here's the situation I wanted to use it in.
1. Regular users have collections of files in their respective Trash.
2. 'root' has some files in Trash.
3. Using 'gksudo nautilus' I deleted several development kernel images from
/boot/ - which is mounted from a separate partition, /dev/sda1.
4. The deletion (to Trash) created /boot/.Trash-0/ and moved the kernel images
there.
5. As a regular user I did 'list-trash' and only saw the files in the user
Trash - good.
6. As super-user I repeated the command (sudo list-trash) and saw the Trash
files belonging to *all* users, plus the files in /boot/.Trash-0/
It isn't clear from the man-page or the --help , but as super-user, it
appears that empty-trash will operate on *all* Trash directories.
There is apparently no way to specify/limit which Trash to operate on,
which is especially annoying when there is a per-partition Trash.
At a minimum this aspect needs properly documenting in the man-pages,
especially the effect of running as super-user (the only way for 'root'
to clear its own Trash) will apparently wipe all other Trash directories
too, regardless of the owning user's preferences.
This should also be pushed upstream as a bug since it could have pretty
unfortunate side-effects.
** Affects: trash-cli (Ubuntu)
Importance: Undecided
Status: New
--
empty-trash removes too much
https://bugs.edge.launchpad.net/bugs/279761
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
