Kent Yoder wrote the following on 09/06/2007 05:47 PM:
Hmm, if you were serving files out of the lower mount, the headers of
the files would look the same like this... Is Apache pointed at the
upper mount?
Yes it is. The lower mount is $HOME/protected/encrypted which is mounted
as an overlay on $HOME/protected. I have also restarted the webserver to
ensure that the webserver did not keep a reference to the lower mount in
some obscure way.
Another fact that indicates that the file from the lower mount is not
served is that the served file contains less information (end is just
zeroes) than the original file.
On 9/6/07, Stefan Farestam <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> When using a directory encrypted with ecryptfs to serve an apache
webserver
> I am only getting garbage. The bizarre thing is that I have no problem
> using the files from the encrypted directory when using other
applications
> such as emacs or the openoffice tools. To add to the mystery, the
files that
> are served are of identical length to the original files and they
all start
> with the roughly the same sequence of bytes (dumped here using "od
-c", note
> the occurrence of the strings "3DUfw" and "_CONSOLE"):
>
> file 1 (standard text file containg html):
> 0000000 \0 \0 \0 \0 \0 017 275 271 207 f p 030 273 347 307 355
> 0000020 002 \0 \0 002 \0 \0 \0 \0 001 214 - 004 \t 003 001
> 0000040 \0 021 " 3 D U f w ` V 364 326 372 366 C R
> 0000060 \v x y 275 033 @ V 5 376 225 | 236 P y 6 3
> 0000100 a , 252 366 257 ? V d z 355 026 b \b _ C O
> 0000120 N S O L E \0 \0 \0 \0 G 3 357 277 366 003 I
> 0000140 216 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
> 0000160 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
>
> file 2 (a tar.gz file):
> 0000000 \0 \0 \0 \0 \0 \0 002 210 ` E 231 375 \ 304 . \b
> 0000020 002 \0 \0 002 \0 \0 \0 \0 001 214 - 004 \t 003 001
> 0000040 \0 021 " 3 D U f w ` I 247 234 1 351 345 271
> 0000060 215 X 241 374 F 005 d 026 023 - { 332 \a G c 245
> 0000100 215 226 k l \a 023 342 332 n 355 026 b \b _ C O
> 0000120 N S O L E \0 \0 \0 \0 G 3 357 277 366 003 I
> 0000140 216 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
> 0000160 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
>
> I first thought that I observed an encoding problem of sorts, but
the fact
> that two completely different files both have these mysterious
sequences in
> the beginning of the file tells me that something else is going on.
>
> System info:
>
> os: Ubuntu Feisty
> kernel: 2.6.21.7 (no patches)
> ecryptfs module: from ecryptfs-20070821.tar.bz2
> ecryptfs utils: from ecryptfs-20070821.tar.bz2
>
> Thanks,
> Stefan
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> eCryptfs-users mailing list
> eCryptfs-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ecryptfs-users
>
>
--
Kent Yoder
IBM LTC Security Dev.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
eCryptfs-users mailing list
eCryptfs-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecryptfs-users
