Comment 6 for bug 317895

I'm on a local system. Nothing from /etc/skel/* was written to my ~ before i chmod'd 700 on ~ and KDE did *not* like that it was 500.

Also, what I see happening with the patch is the following (consider user "test3"):
Before test3 logs in:
drwxr-xr-x 5 test3 test3 4096 2009-02-22 03:59 test3
After test3 logs in:
drwx------ 30 test3 test3 12288 2009-02-22 03:59 test3

Before the patch, when a user setup with ecryptfs bootstrapping is logged in (and thus the drive should be unencrypted), the permissions are 500.

The patch does not affect what the permissions are when the user isn't logged in. In the case that the encrypted directory is not mounted, the mountpoint (~) is 755 regardless. The 55 doesn't matter so much since the files all display as empty to any other user, but that 7 could screw up what you're saying about unencrypted files that go invisible post-mounting.

I think what you're describing would require changing the before-mounting permissions to 555 and having the post-mounting permissions be 700. The patch only covers the latter part of that.