ecryptfs team mailing list archive

[syscon-hh <syscon.kono@xxxxxxxxxx>]

Public bug reported:

Binary package hint: ecryptfs-utils

- ecryptfs-utils_73-0ubuntu6 with Jaunty
- ecryptfs-utils_75-0ubuntu1 with Karmic

Trying to discover data from a crashed system with encrypted home-
directory, it is recomended to use:

sudo mount -t ecryptfs /home/<username>/.Private  /home/<username>

But after inserting the passphrase and answering the shown options, the
volume is mounted to the given mount-point - but the name of files - and
volumes are still encrypted, The content is partly readable.

It seem to me. the following is running wrong -> On a healthy system you
will find inside /etc/mtab:

"ecryptfs_sig=14140887552e0bec,ecryptfs_fnek_sig=de5d090606c60111,ecryptfs_cipher=aes,ecryptfs_key_bytes=16",
with different _sig values

but on a broken system after using above command both values are the
same

"ecryptfs_sig=14140887552e0bec,ecryptfs_fnek_sig=14140887552e0bec,ecryptfs_cipher=aes,ecryptfs_key_bytes=16",
independent of choosing (y/ n) for plaintext as well for foldername
decryption (y/n).

These have been testet and validated with Jaunty and Karmic - both the
same results.

** Affects: ecryptfs-utils (Ubuntu)
     Importance: Undecided
         Status: New

-- 
mount -t ecryptfs for extern discovery fails
https://bugs.launchpad.net/bugs/383059
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: New

Bug description:
Binary package hint: ecryptfs-utils

- ecryptfs-utils_73-0ubuntu6 with Jaunty
- ecryptfs-utils_75-0ubuntu1 with Karmic

Trying to discover data from a crashed system with encrypted home-directory, it is recomended to use:

sudo mount -t ecryptfs /home/<username>/.Private  /home/<username>

But after inserting the passphrase and answering the shown options, the volume is mounted to the given mount-point - but the name of files - and volumes are still encrypted, The content is partly readable.

It seem to me. the following is running wrong -> On a healthy system you will find inside /etc/mtab:

"ecryptfs_sig=14140887552e0bec,ecryptfs_fnek_sig=de5d090606c60111,ecryptfs_cipher=aes,ecryptfs_key_bytes=16", with different _sig values

but on a broken system after using above command both values are the same

"ecryptfs_sig=14140887552e0bec,ecryptfs_fnek_sig=14140887552e0bec,ecryptfs_cipher=aes,ecryptfs_key_bytes=16", independent of choosing (y/ n) for plaintext as well for foldername decryption (y/n).

These have been testet and validated with Jaunty and Karmic - both the same results.