Comment 7 for bug 725862

I noticed that the hex value is different after a successful mount, and after that I have two keys in @u, one with each value. Then ecryptfs-umount-private deletes the “right” one but leaves the “wrong” one around:

anders@fixed-disk:~$ keyctl clear @u
anders@fixed-disk:~$ keyctl list @u
keyring is empty
anders@fixed-disk:~$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [6a0a0dc419b62549] into the user session keyring
anders@fixed-disk:~$ keyctl list @u
2 keys in keyring:
571793771: --alswrv 1000 1000 user: c2e0b8f13ee13855
704793275: --alswrv 1000 1000 user: 6a0a0dc419b62549
anders@fixed-disk:~$ ecryptfs-umount-private
anders@fixed-disk:~$ keyctl list @u
1 key in keyring:
571793771: --alswrv 1000 1000 user: c2e0b8f13ee13855
anders@fixed-disk:~$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [c2e0b8f13ee13855] into the user session keyring
keyctl_search: Required key not available
Perhaps try the interactive 'ecryptfs-mount-private'