Filenames in ~/.Private are not encrypted
Bug #264977 reported by
ehcpdeveloper
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
Critical
|
|||
ecryptfs-utils (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
As Per https:/
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 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.
Related branches
description: | updated |
Changed in ecryptfs-utils: | |
status: | Confirmed → Triaged |
Changed in ecryptfs: | |
importance: | Unknown → Critical |
status: | Unknown → Fix Released |
To post a comment you must log in.
Thanks for your report. Affecting to ecryptfs-utils and confirmed in Intrepid.
j-lallement@ black:/ tmp$ lsb_release -rd; apt-cache policy ecryptfs-utils
Description: Ubuntu intrepid (development branch)
Release: 8.10
ecryptfs-utils:
Installed: 53-1ubuntu8
Candidate: 53-1ubuntu8
Version table:
*** 53-1ubuntu8 0