ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

I use Evolution and Encrypted Home, and I've never seen this issue.

However, I certainly agree that there are situations when the home
directory is not unmounted because of lingering processes.  This is
required to protect your data.

I'm marking the bug against ecryptfs invalid, as this is behavior by
design.  The better question is why evolution is doing something like
this.

** Changed in: ecryptfs-utils (Ubuntu)
       Status: New => Invalid

-- 
Automatic umount ineffective on standard installation
https://bugs.launchpad.net/bugs/507231
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” package in Ubuntu: Invalid
Status in “evolution-data-server” package in Ubuntu: New

Bug description:
Binary package hint: ecryptfs-utils

In a standard ubuntu installation, the evolution-data-server application is started when the user first logs in and keeps running even after the user has logged out. This prevents ecryptfs from automatically umounting the encrypted home directory and keeps the unencrypted data available until the computer is restarted.

Steps to reproduce:
 - Log in to GDM as a user with ecryptfs encrypted home directory
 - Log out
 - Switch to console, log in as root
 - Observe that the home directory of the user is still mounted