ecryptfs create Private dir with wrong permissions

Bug #363876 reported by Paolo Benvenuto
2
Affects Status Importance Assigned to Milestone
ecryptfs-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ecryptfs-utils

I issued:

$ sudo aptitude install ecryptfs-utils
$ ecryptfs-setup-private

I got;

Private dir had permissions dr-x------, i.e. it was 500, not 700

besides that, mount didn't reported any dir Private mounted

Revision history for this message
Paolo Benvenuto (donpaolo) wrote :

jaunty RC

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

This is by design, not a bug.

When the private directory is not mounted, the permissions are 500 so that you don't inadvertently write data to the unecrypted mountpoint.

Once it's mounted, then the permissions will be 700.

Did you log out and log back in to see if the automount takes place?

:-Dustin

Changed in ecryptfs-utils (Ubuntu):
status: New → Invalid
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.