as a trainer, one of the banes of my existence is the omission of sometimes critical bits of info in the midst of a set of instructions. for an upcoming class, i wanted to show a simple example of how to use ecryptfs to create a simple encrypted "Private" directory, so i googled and found one over at archlinux:
https://wiki.archlinux.org/index.php/ECryptfs
seems like that would work for any recent distro, so i decided to start by running the "simple" example:
https://wiki.archlinux.org/index.php/ECryptfs#Setup_.28simple.29
as a regular user on my fedora 20 system, and immediately got:
ERROR: User needs to be a member of ecryptfs group
sure enough, the wrapper script ecryptfs-setup-private explicitly checks that the caller is a member of that existing group, but the archlinux page doesn't mention that requirement and neither does the man page for that script on fedora.
while this sounds niggling, it is one of the things that can drive someone a bit batty as they (me) think, "wait ... did i miss something? did i not read properly?" is this something that deserves a low-priority bug report to mention this in the man page?
rday
On Sat, 28 Dec 2013 03:24:44 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
while this sounds niggling, it is one of the things that can drive someone a bit batty as they (me) think, "wait ... did i miss something? did i not read properly?" is this something that deserves a low-priority bug report to mention this in the man page?
https://launchpad.net/ecryptfs
On Sat, 28 Dec 2013, Frank Murphy wrote:
On Sat, 28 Dec 2013 03:24:44 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
while this sounds niggling, it is one of the things that can drive someone a bit batty as they (me) think, "wait ... did i miss something? did i not read properly?" is this something that deserves a low-priority bug report to mention this in the man page?
ah, thank you.
rday
On Sat, 28 Dec 2013, Frank Murphy wrote:
On Sat, 28 Dec 2013 03:24:44 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
while this sounds niggling, it is one of the things that can drive someone a bit batty as they (me) think, "wait ... did i miss something? did i not read properly?" is this something that deserves a low-priority bug report to mention this in the man page?
ironically, i just checked out the source from upstream, and exactly that addition had been made to the man page. :-)
rday