[Gutsy] attempt to create archive in dir without writing permissions creates archive in user home without notification

Bug #186583 reported by lunchtime
254
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: file-roller

Concerns: Ubuntu Gutsy Gibbon, file-roller 2.20.1-0ubuntu1

I found a "--" tarball with root owned files in my user home directory. The origin of this file was initially unclear but I managed to reproduce this file as follows:

- as a normal user open nautilus and go to /root
- select some files (not directories) for which the user has reading rights (rw-r--r--)
- right click to create an archive in the same directory

Trying to create an archive in the directory where the user doesn't have writing rights will fail without an error message.

Here's the problem: Without any notification, a tarball named "--" (without extension), which includes the root-owned files, is now placed in the home directory of the user who attempted to create the archive in the root directory. Any new attempt will append files to this archive.

File-roller shouldn't create an archive in any other location than the one specified by the user.

Revision history for this message
Christoph Langner (chrissss) wrote :

I can confirm this except the fact, that i don't get an error message, when trying to create an archive in e.g. /root. But i also find a tarball called "--" inside $HOME after that attempt.

Changed in file-roller:
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report. the intrepid version automatically change the selected directory to the user one in such cases, could you try if you still get the issue in hardy or intrepid?

Changed in file-roller:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in file-roller:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.