mlocate does not work as expected on encrypted disks

Bug #578303 reported by Rolf Leggewie
This bug report is a duplicate of:  Bug #827841: Add /home/.ecryptfs to PRUNEPATHS. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mlocate (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: mlocate

My home partitions were set up with ecryptfs (an option in the installer). locate now does not return original filenames, but hashed ones,
unlegible stuff under /home/.ecryptfs/rolf/.Private/

There's two things that need to be done, I think

1) don't index stuff under */.ecrypts/*
2) do index /home/$user

Tags: lucid
Rolf Leggewie (r0lf)
summary: - mlocate does not work on encrypted disks
+ mlocate does not work as expected on encrypted disks
Revision history for this message
bitinerant (bitinerant) wrote :

As I understand it, this is intentional! I agree that in theory this aught to work, but mlocate would need to be completely redesigned to address the security issue. Note that 'ecryptfs' is in the 'PRUNEFS=' line of the default /etc/updatedb.conf file. I suppose you could edit this file to 'fix' this problem, but know that your encrypted metadata (file and directory names) will be readable by anyone who steals your computer. See:

  https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/372631

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.