ecryptfs team mailing list archive

Thread
Date

[Bug 264977] Re: Filenames in ~/.Private are not encrypted

To: ecryptfs@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <264977@xxxxxxxxxxxxxxxxxx>
Date: Mon, 26 Jan 2009 19:50:09 -0000
Reply-to: Bug 264977 <264977@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package ecryptfs-utils - 69-0ubuntu1

---------------
ecryptfs-utils (69-0ubuntu1) jaunty; urgency=low

  * New upstream release, dropped all patches (included upstream)
  * This release includes support for filename encryption (LP: #264977)
  * This release promotes keyutils from a 'recommends' to a 'depends,
    for access to the keyctl command, which is used by the helper scripts
    to clear the keyring on unmount (LP: #313812)

 -- Dustin Kirkland <kirkland@xxxxxxxxxx>   Mon, 26 Jan 2009 13:51:21
-0500

** Changed in: ecryptfs-utils (Ubuntu)
       Status: Triaged => Fix Released

-- 
Filenames in ~/.Private are not encrypted
https://bugs.launchpad.net/bugs/264977
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Unknown
Status in “ecryptfs-utils” source package in Ubuntu: Fix Released

Bug description:
As Per https://wiki.ubuntu.com/EncryptedPrivateDirectory I created a private directory.
Ii mounted it, then put some files in it.
Then unmounted the Private dir.
~/Private contains only "THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA --  Run mount.ecryptfs_private to mount again"


~/.Private still contains all the private files, albeit the contents are indeed encrypted... 

I had expected that the filesystem of ~/Private would also be encrypted so that a potential data thief would not even know what files I have on my system.