On Wed, 19 Dec 2007, Michael Halcrow wrote:
-> > The test with one file on this machine was OK, but soon as I put it
-> > into real use on another machine and tried to do a mount, the mount
-> > fails on empty directories. It says something about not being able
-> > to resolve a full path, but th
On Tue, Dec 18, 2007 at 10:44:06AM -0500, jayjwa wrote:
> The test with one file on this machine was OK, but soon as I put it
> into real use on another machine and tried to do a mount, the mount
> fails on empty directories. It says something about not being able
> to resolve a full path, but ther
The test with one file on this machine was OK, but soon as I put it into real
use on another machine and tried to do a mount, the mount fails on empty
directories. It says something about not being able to resolve a full path,
but there's nothing special about the directory /var/cache/ecryptfs/
I gave #35 a go, this release seems much better. No major problems noted so
far, only one error about GPG:
ecryptfsd: Error initializing key module
[/usr/lib/ecryptfs/libecryptfs_key_mod_gpg.so]; rc = [-22]
To my knowlege, GPG is not yet supported...is it?
mount -t ecryptfs -o
verbose,key=op
