Comment 7 for bug 283477

Revision history for this message
Kyle M Weller (kylew) wrote : Re: [Bug 283477] Re: ecryptfs-utils does not handle changing password

omg this bug really sucks I cant even copy my data what do I do next, thanks
for the help

On Tue, Oct 14, 2008 at 8:37 PM, defcon <email address hidden> wrote:

> im also getting:
> Input/output error
> when trying to open files in /mnt where it mounted
>
> On Tue, Oct 14, 2008 at 5:00 PM, Dustin Kirkland <
> <email address hidden>> wrote:
>
>> Start by retrieving the mount passphrase:
>> $ ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase
>> LOGIN_PASSWORD
>>
>> If any errors occur, you're probably not giving the correct
>> LOGIN_PASSWORD. When you do, it will just display the MOUNT_PASSPHRASE
>> on standard out.
>>
>> To access your data, you always can manually mount as root with the
>> MOUNT_PASSPHRASE:
>> $ sudo mount -t ecryptfs ~/.Private /mnt
>> (3) passphrase
>> MOUNT_PASSPHRASE
>> (1) aes
>> (1) 16 bytes
>> (n) no plaintext passthrough
>> (yes) proceed with the mount as root
>> (yes) add to signature cache
>>
>> Or, to mount as yourself, you can manually insert the MOUNT_PASSPHRASE
>> into your kernel keyring and then mount with:
>> $ ecryptfs_insert_wrapped_passphrase_into_keyring
>> ~/.ecryptfs/wrapped-passphrase LOGIN_PASSWORD
>> $ mount.ecryptfs_private
>> $ ls ~/Private
>>
>> To fix this for your next boot, you may need to:
>> $ ecryptfs_rewrap_passphrase ~/.ecryptfs/wrapped-passphrase
>> PREVIOUS_LOGIN_PASSWORD NEW_LOGIN_PASSWORD
>>
>> The PAM password change module has been hooked by pam_ecryptfs, so all
>> of this should have happen automatically. Can you tell me any more
>> about how you worked did this, in case there's an actual bug here?
>>
>> :-Dustin
>>
>> ** Changed in: ecryptfs-utils (Ubuntu)
>> Status: New => Incomplete
>>
>> ** Changed in: ecryptfs
>> Status: New => Incomplete
>>
>> --
>> ecryptfs-utils does not handle changing password
>> https://bugs.launchpad.net/bugs/283477
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>