ecryptfs team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

I don't think it makes sense at all in gdm:

 - You do not actually "see" gdm if you have autologin enabled.
 - Once you installed your system that way, the damage is done.

IMHO it should be pointed out right at the place when the user can still
do something about it to not break it: The autologin and ecryptfs
options should mutually exclude themselves in the installer.

Ideally, if you create an ecryptfs with command line tools in an
installed system,  it would point out that it doesn't work with
autologin, but that would encode gdm specific knowledge into the
scripts, so we should avoid that. It could just generally tell the user
about it.

But it is totally doable in the installer.

** Changed in: gdm (Ubuntu)
       Status: New => Incomplete

-- 
Encrypted Private Directory is not automatically mounted when using gdm auto-login
https://bugs.launchpad.net/bugs/284443
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: Won't Fix
Status in “gdm” source package in Ubuntu: Incomplete

Bug description:
if autologin is enabled in gdm, the encrypted private directory is not automatically mounted 

as ubiquitiy now has an autologin option, this will affect many users who later manually create an encrypted directory

from the security point of view, no auto mount for auto login this is certainly good and not a 'bug'; but it is unexpected and should be documented; also, both ecryptfs-utils and gdmsetup should explicitly warn for this case