Oct 14 20:24:01 ion ecryptfs-insert-wrapped-passphrase-into-keyring: Error
attempting to parse .ecryptfsrc file; rc = [-5]
Oct 14 20:24:02 ion ecryptfs-insert-wrapped-passphrase-into-keyring:
Incorrect wrapping key for file [/home/defcon/.ecryptfs/wrapped-passphrase]
Oct 14 20:24:02 ion ecryptfs-insert-wrapped-passphrase-into-keyring: Error
attempting to unwrap passphrase from file
[/home/defcon/.ecryptfs/wrapped-passphrase]; rc = [-5]
On Tue, Oct 14, 2008 at 8:22 PM, defcon <email address hidden> wrote:
> Unable to read salt value from user's .ecryptfsrc file; using default
> Error attempting to unwrap passphrase and insert into the user session
> keyring; rc = [-5]. Check the system log for more information from
> libecryptfs.
> What does this mean?
>
>
>
> 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.
>>
>
>
Oct 14 20:24:01 ion ecryptfs- insert- wrapped- passphrase- into-keyring: Error insert- wrapped- passphrase- into-keyring: defcon/ .ecryptfs/ wrapped- passphrase] insert- wrapped- passphrase- into-keyring: Error defcon/ .ecryptfs/ wrapped- passphrase] ; rc = [-5]
attempting to parse .ecryptfsrc file; rc = [-5]
Oct 14 20:24:02 ion ecryptfs-
Incorrect wrapping key for file [/home/
Oct 14 20:24:02 ion ecryptfs-
attempting to unwrap passphrase from file
[/home/
On Tue, Oct 14, 2008 at 8:22 PM, defcon <email address hidden> wrote:
> Unable to read salt value from user's .ecryptfsrc file; using default unwrap- passphrase ~/.ecryptfs/ wrapped- passphrase insert_ wrapped_ passphrase_ into_keyring wrapped- passphrase LOGIN_PASSWORD private rewrap_ passphrase ~/.ecryptfs/ wrapped- passphrase LOGIN_PASSWORD NEW_LOGIN_PASSWORD /bugs.launchpad .net/bugs/ 283477
> Error attempting to unwrap passphrase and insert into the user session
> keyring; rc = [-5]. Check the system log for more information from
> libecryptfs.
> What does this mean?
>
>
>
> On Tue, Oct 14, 2008 at 5:00 PM, Dustin Kirkland <
> <email address hidden>> wrote:
>
>> Start by retrieving the mount passphrase:
>> $ ecryptfs-
>> 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_
>> ~/.ecryptfs/
>> $ mount.ecryptfs_
>> $ ls ~/Private
>>
>> To fix this for your next boot, you may need to:
>> $ ecryptfs_
>> PREVIOUS_
>>
>> 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:/
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>