Please see the upstream eCryptfs FAQ:
 * http://ecryptfs.sourceforge.net/ecryptfs-faq.html#filename-enc

In brief, there are some complex problems with filename encryption,
however, it is a known feature-request, and a the upstream authors
plan to implement it at some point.

Quoting here:
  Q. What about filename encryption?

  The namespace problem arises when we consider the case
  where two files have the same unencrypted name. This can
  be a problem when the user does not have the key for every
  file in any given directory. Imagine, for instance, that Alice
  creates a file named ``meeting_notes.txt'' in a shared directory
  on an NFS server. The filename is encrypted with a key known
  only to Alice and Carol. Bob then creates a file in the same
  shared NFS directory and also names it ``meeting_notes.txt'',
  encrypting the filename with another key only known to Bob
  and Carol. Bob's eCryptfs client cannot detect the unencrypted
  filename conflict in the namespace because Bob does not have
  Alice's key.

  So two different files that have the same unencrypted name and
  different encrypted names appear in the same directory. When
  Carol, who has both Alice's key and Bob's key, lists the contents
  of the directory, he winds up seeing two different files with the same
  filename in the same directory, which is a POSIX violation.

  The solution we may implement is to use a separate key just for
  filename encryption, requiring all filenames encrypted under any
  given directory to be encrypted with that key. Filename encryption
  is a planned feature, but there is currently no set date for when it
  will be completed.


:-Dustin

** Bug watch added: SourceForge.net Tracker #1618003
   http://sourceforge.net/support/tracker.php?aid=1618003

** Also affects: ecryptfs via
   http://sourceforge.net/support/tracker.php?aid=1618003
   Importance: Unknown
       Status: Unknown

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to