Bug 709158

Summary: ecryptfs-migrate-home doesn't setup the directory properly
Product: [Fedora] Fedora Reporter: Christoph Dräger <sandman.slayer>
Component: ecryptfs-utilsAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: esandeen, mhlavink, redhat-bugzilla, sven.jost
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:21:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 712048    
Bug Blocks:    

Description Christoph Dräger 2011-05-30 21:30:01 UTC
Description of problem:
On a fresh installed F15 with all normal updates and installed ecryptfs-utils, the ecryptfs-migrate-home-skript doesn't setup a home-directory properly.
As root I started: ecryptfs-migrate-home -u test
without problems. Then i logged-in with user test as the script said to do:

fedora-vm home]$ su test
bash-4.2$ cd test
bash-4.2$ ls
Access-Your-Private-Data.desktop  README.txt

So auto-mount didn't work but this is not the real problem I think because:

bash-4.2$ ecryptfs-mount-private 
ERROR: Encrypted private directory is not setup properly

Any idea how to produce usable log-files or something like that? dmesg and messages don't tell anything about this problem.

Version-Release number of selected component (if applicable):
ecryptfs-utils 86-1.fc15

How reproducible:
100%

Steps to Reproduce:
1. install a new Fedora F15 and update
2. create a user and add him the to ecryptfs-group
3. as root run "ecryptfs-migrate-home -u *user*"
4. log-in as *user*
  
Actual results:
home-directory is not setup properly

Expected results:
home-directory is setup properly and automount of the encrypted container works.

Additional info:

Comment 1 Michal Hlavinka 2011-05-31 06:20:19 UTC
this is known, because login automount does not work in Fedora (yet). Support for ecryptfs has been added to pam (authconfig) just recently and other parts are not in place yet. Work in progress

Comment 2 Michal Hlavinka 2011-06-09 10:57:48 UTC
I was able to reproduce this. Situation here is not that bad as I thought :)
There is only really small piece missing to make it work from ecryptfs-utils POV, I'll add it right now. Unfortunately SELinux does not like this and requires some changes. I'm going to open bz for this.

Comment 3 Michal Hlavinka 2011-06-09 12:46:27 UTC
Everything is ready, just waiting for blocking selinux bug...

Comment 4 Michal Hlavinka 2011-07-29 08:31:31 UTC
*** Bug 703145 has been marked as a duplicate of this bug. ***

Comment 5 Kevin R. Page 2012-06-03 00:34:36 UTC
The problem still exists in Fedora 17. It looks like it's still the selinux problem. I've tested instructions in bug #712048 comment #17 without success.

Comment 6 Michal Hlavinka 2012-06-04 14:53:31 UTC
I know about it, it's the reason why this bug is not marked as fixed. We are still waiting for selinux guys to fix their part.

Comment 7 Fedora End Of Life 2012-08-07 20:21:15 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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