Bug 754703

Summary:	ecryptfs kernel modules not loaded timely when logging in via GDM
Product:	[Fedora] Fedora	Reporter:	arturj <artur>
Component:	ecryptfs-utils	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	esandeen, mhlavink
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-02 14:51:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description arturj 2011-11-17 12:52:22 UTC

Description of problem:
kernel modules not loaded timely upon login via GDM. Possibly race-condition?

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


How reproducible:
setup ecryptfs and migrate users home. workaround all selinux issues or disable selinux. reboot and login via GDM. user directory gets mounted but undecrypted, so all the encrypted files are within the users home instead only decrypted files. logging in via CLI after reboot works well. my current fix is to load ecryptfs-kernel-module statically via modules-load.d on boot.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
user can't log in properly via GDM once his home was migrated to ecryptfs

Expected results:
user logs in via GDM and CLI and gets his files decrypted automatically

Additional info:

Comment 1 Michal Hlavinka 2011-11-23 09:55:32 UTC

I've just tried to reproduce this (with selinux set to permissive mode), but everything is working fine for me. 

> workaround all selinux issues 

how did you do this exactly?

Please try to reproduce this problem and attach your /var/log/messages and /var/log/secure

Thanks

Comment 2 Michal Hlavinka 2012-04-02 14:51:29 UTC

Needinfo state for a looong time. Closing as insufficient_data. 

If you still see this bug and can provide requested data, feel free to reopen.