On Sat, Sep 08, 2007 at 04:36:06PM -0500, Trevor Highland wrote:
> I was able to reproduce what you are seeing. I turned on debug
> statements and discovered a few things that stand out. When a file
> is accessed through apache the file is opened properly through
> ecryptfs, which includes reading
On Sat, Sep 08, 2007 at 01:20:17PM -0700, Stefan Farestam wrote:
> [drm] writeback test succeeded in 2 usecs
> BUG: unable to handle kernel NULL pointer dereference at virtual address
>
> printing eip:
>
> *pde =
> Oops: [#1]
...
> EIP:0060:[<>]Taint
Hi,
I was able to reproduce what you are seeing. I turned on debug statements
and discovered a few things that stand out. When a file is accessed through
apache the file is opened properly through ecryptfs, which includes reading
the header of the file. Once the file is open I see no sign of eCr
Hi again,
When using ecryptfs to encrypt a home directory under Gnome/Ubuntu, I am
seeing ecryptfs crash. Excerpt from dmesg below. Here is the procedure
that I followed:
* login as root
* create a new account called "tadm"
* remove the created home directory and recreate
% rm -
As a change to all of my recent bug reports, I would like to share a
simple method to mount/unmount encrypted directories when gnome sessions
are started and ended.
I found a package called "libpam_script" which allows custom scripts to
be executed when a session is started and ended. I didn
You were right Michael, this one was due to extra options that added by
mount. The manual page for "mount" (on Ubuntu) states the following for
the option "user":
This option implies the options noexec, nosuid, and nodev
(unless overridden by subsequent options, as in the option
line u
Hi again,
I've investigated a bit more thoroughly into this problem, but I am
still observing the same strange behavior. This time around I used
strace on the apache server process and verified that apache did indeed
only access the unencrypted file ($HOME/b/testfile.txt in the example
below)
