Is the file “/lib/security/pam_ecryptfs.so” there? I do see it on my system.
I haven’t noticed that message, but then I haven’t been looking for it. What I do find, is that after installing it still does not work automatically. So I need to do:
# pam-config -a --ecryptfs
Maybe there’s a bug in the postinstall scriptlet (perhaps it is run too early).
I’m not sure, but I think it works the second time. If not, then in a root shell, run:
modprobe ecryptfs
This doesn’t happen with normal use, but it does happen the first time for the first user after boot. Once the ecryptfs private directory is set to open on login, it should work without this problem.
Put sensitive files in the Private directory (or a subdirectory under there). They look unencrypted to you, but they are actually stored encrypted on the disk.
If you look at your directory “.Private”, that’s where the encrypted files really are. You will have trouble making sense of that directory, because of the encryption. But once your private directory is mounted (which happens automatically on login), you see a virtual copy of the file which you see unencrypted, because “ecryptfs” is handling that behind the scenes.