Hello all, I believe there is an error in the ecryptfs-recover-private script that was exposed when I tried to mount my ecryptfs manually on my recently updated Arch Linux system (some of the ecryptfs setup was done when the same RAID drive was attached to an Ubuntu Linux system). First I issued an ecryptfs recover command: ecryptfs-recover-private /home/.ecryptfs/bpotter/.Private This will: Find the directory, I tell it to recover (yes) It finds the wrapped passphrase, I tell it yes I know my login password and enter it It inserts token with correct sig into the keyring, but then errors out with this error: sed: can't read /home/.ecryptfs/bpotter/.Private/../.ecryptfs/Private.sig:... No such file or directory At this point I run 'sudo mount /home/bpotter', which mounts as per my fstab: /home/.ecryptfs/bpotter/.Private /home/bpotter ecryptfs... rw,user,noauto,exec,relatime,ecryptfs_fnek_sig=07fa32a41b76c74a,... ecryptfs_sig=07fa32a41b76c74a,ecryptfs_cipher=aes,... ecryptfs_key_bytes=32,ecryptfs_passthrough,... ecryptfs_unlink_sigs 0 0 Next it asks me to select the key type for newly created files. I pick 2) passpharse and give it my login passphrase. It tells me it hasn't seen this combination, but mounts just fine. I can read and write all of my files. I covered this and tried to find an answer as to why this is happening in Stack Exchange's Super User as well: http://superuser.com/questions/507948/ecryptfs-home-directory-does-not-automatically-mount I just wanted to inform the list of the possible error in the ecryptfs-recover-private script. If anyone can help me find why my automatic mounting has failed, then that's a bonus. Thanks, B. J. Potter -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
