Bug 806410

Summary: File roller creates temporary files outside the encrypted partition
Product: [Fedora] Fedora Reporter: Marco Motta <marco.motta>
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 18:32:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marco Motta 2012-03-23 16:20:55 UTC
Description of problem:

If I create or open a file in an encrypted partition, temporary files are not created in the encrypted partition, but in /home/user/.cache. So all the files become accessible for recovery without need of passwords.
Note that, if I mount a ramdisk with the command
mount -t tmpfs -o size=1024M tmpfs /home/user/.cache
file-roller ignore the dir /home/user/.cache, and save temporary files direcly in /home/user.

Version-Release number of selected component (if applicable):3.2.1


How reproducible:
Open a file from an archive saved in a crypted partition (as a luks file). 

Steps to Reproduce:
1. Open a file from an archive saved in a crypted partition (as a luks file).
2. Type (as root) mount -t tmpfs -o size=1024M tmpfs /home/user/.cache
  
Actual results:
1. Temporary files are saved in /home/user/.cache, that is not inside a crypted file or partition.
2. If a ramdisk is mounted in /home/user/.cache, the dir is ignored, and temporary files are saved outside the ramdisk.

Expected results:
Temporary files saved inside the crypted partition, or at least into the ramdisk, if mounted in /home/user/.cache

Additional info:

Comment 1 Marco Motta 2012-03-25 20:10:23 UTC
To fix, execute from terminal the following script:

########################################################################
su -c "yum install libglade2-devel gnome-doc-utils rpm-build rpmdevtools"
cd ~
mkdir -p file-roller-with-patch
cd file-roller-with-patch
yumdownloader --source file-roller
rpm2cpio file-roller*.rpm | cpio -ivd
VERSION=`grep "Version" file-roller.spec | sed 's/Version://g' | sed 's/ //g'`
rm file-roller-$VERSION*.rpm
tar -xJvf file-roller-$VERSION.tar.xz
rm file-roller-$VERSION.tar.xz
sed -i 's/"cache", "~", "tmp"/"cache"/g' file-roller-$VERSION/src/file-utils.c
tar -cJvf file-roller-$VERSION.tar.xz file-roller-$VERSION
rm -rf file-roller-$VERSION
mkdir -p ~/rpmbuild/SOURCES
mv file-roller-$VERSION.tar.xz ~/rpmbuild/SOURCES
rpmbuild -v -bb file-roller.spec
cd ~/rpmbuild/RPMS/x86_64 #modify for 32 bit
su -c "yum remove file-roller; rpm -iv file-roller*.rpm"
########################################################################

Now, you have a modified file-roller that always save temporary files in /home/user/.cache. Before working with archives in crypted partitions, type:

mount -t tmpfs -o size=1024M tmpfs /home/user/.cache

to create a ramdisk for temporary files. Replace "user" (after "home" and before ".cache") with your user name in the last command.
N.B. Do not mount the ramdisk automatically at boot, and umount it when you end, because if file-roller must work with very big files it can be insufficient.

Comment 2 Fedora End Of Life 2013-01-16 15:31:42 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 18:32:44 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.