Hot answers tagged ecryptfs
This guide is pretty major surgery, only follow it if you are confident at the command line - a few mistakes could lead to losing all your data. You will have to copy all the files from your home directory somewhere else, and then copy them back once you have turned off the encryption, but you don't have to reinstall. So let's say you have an external drive ...
Are you sure that /home/.ecryptfs/A is locked for reading? I use ecryptfs and while I'm logged in and can browse and read the files in /home/.ecryptfs/myusername/.Private. I just tried going into that directory (and sub-directories) and opening files (using vim -b) and I could read them fine. I'd certainly want them locked for writing, but I don't see why ...
eCryptFS does not support ACLs, but apparently there are some people working on that. See: http://188.8.131.52/~rdhaliwal/Final_Report.pdf THE file system eCryptfs aims at providing advanced security mechanism for file systems using existing cryptographic technologies. It provides several policy features but does not provide Access Control ...
According to Tyler Hicks (one of the maintainers of eCryptfs) it is currently not safe to modify underlying filesystem (lower filesystem in eCryptfs terminology): It would be good if eCryptfs could detect lower file data changes and update the cache to see the file updated. Even if we could detect them, how would we mediate them against ...
Remove auto-umount file from ~/.ecryptfs/ - each time you will need to umount your private directory manually. The other option is to keep your ssh session running using screen or tmux. More info on ecryptfs Ubuntu
Presumably the passphrase of the user not present is absolutely needed for decryption. Hence your only option is to look for a solution that backs up encrypted files, and use this for both users. This has the advantage that the apparently confidential information is also encrypted on the backup media - which can be important if you're transferring it around ...
The problem is that pam_ecryptfs captures and uses your login passphrase to decrypt ~/.ecryptfs/wrapped-passphrase, and perform your home directory mount. Unfortunately the non-interactive dovecot pam session that you describe doesn't ever actually snag your login passphrase, so it cannot perform the mount. Sorry.
To update files in the ecryptfs filesystem you need to update them in the mount point - in the encrypted filesystem you would need to update the entire thing at once, as it has no concept of files or directories - it is just a large chunk of data. Yes, you can use rsync to back that data up somewhere, but in order to read or write a particular file you need ...
Only answer seems to be to ignore it and carry on. For anyone else with the same issue here is a rule to hide the error from the logs Add to /etc/rsyslog.conf (Or equiv) :msg, contains, "Error getting passwd info for user" ~ Just ensure it is above any other rules (that might catch it)
Only top voted, non community-wiki answers of a minimum length are eligible