If one trips over this bug, it may cause problems if that broken session creates files that shadow the old, valuable filenames that are encrypted.
If one is using the recommended scheme active during Karmic (at least), then this will find cleartext filenames that should not exist:
$ ls -A /home/.ecryptfs/$USER/.Private |grep -v ECRYPTFS_FNEK
You might have a dozen or so. Move those to a new location, and after log out and unmount of that ecryptfs layer, and remount, the old files will reappear.
If one trips over this bug, it may cause problems if that broken session creates files that shadow the old, valuable filenames that are encrypted.
If one is using the recommended scheme active during Karmic (at least), then this will find cleartext filenames that should not exist:
$ ls -A /home/. ecryptfs/ $USER/. Private |grep -v ECRYPTFS_FNEK
You might have a dozen or so. Move those to a new location, and after log out and unmount of that ecryptfs layer, and remount, the old files will reappear.
Something like this should help clean up:
$ mkdir ~/Desktop/ ecryptfs- bad-for- review ecryptfs/ $USER/. Private/ ecryptfs/ $USER/. Private |grep -v ^ECRYPTFS_FNEK |while read filename; mv -i "/home/ .ecryptfs/ $USER/. Private/ $filename" ~/Desktop/ ecryptfs- bad-for- review/ ; done mount-private
$ mv /home/.
$ ls -A1 /home/.
$ cd /home; sudo umount $USER
$ ecryptfs-