Comment 3 for bug 257901

Based on Dustin's comments it appears that checking the automount option should simply create ~/.ecryptfs/auto-mount whilst unchecking it should remove that file. The initial state of the checkbox should be reflect the existence, or otherwise, of that file.

I notice that Dustin also mentions an auto-unmount option. This would presumably be useful if the user wants a process to be able to access the decrypted files after logout, via a cron job or similar. I think if we're in the realms of cron jobs then the user can be considered advanced enough to create their own file, so I would suggest that the auto-unmount option be left out of this application.

I think we also need to consider the terminology used to refer to the ~/Private directory and the act of (un)mounting it. I would suggest text something like this (with reference to the lines on the screenshot):

"Your Private directory is currently encrypted" (when the directory is unmounted, preceded by an icon)
"Your Private directory is currently unencrypted" (when the directory is mounted, preceded by an icon)

"Decrypt your Private directory" (on the button when the directory is unmounted)
"Encrypt your Private directory" (on the button when the directory is mounted)

"Automatically decrypt your Private directory at login" (by the checkbox)