1 |
As they say, security comes at the cost of convenience (and storage in |
2 |
this case), so I think the most secure solution is to just copy over the |
3 |
data I need to publish to the chroot. I've given it thought, and I don't |
4 |
want the potential apache hax0r to get to (and potentially delete) all |
5 |
my original pictures/videos. The downside is that I'll probably have 90% |
6 |
of them copied to the /chroot/www directory for publishing. |
7 |
|
8 |
The mount --bind thing looked nice, but you can't change the mount |
9 |
permissions from what those directories already have, i.e. if I have |
10 |
/stuff/pics on a filesystem mounted rw, I can't then mount --bind it to |
11 |
ro. At least that's what the man page says. If I could mount it to ro, |
12 |
that might be a better alternative. |
13 |
|
14 |
Thanks, |
15 |
Brian |
16 |
|
17 |
Hans-Werner Hilse wrote: |
18 |
> Hi, |
19 |
> |
20 |
> On Mon, 13 Nov 2006 12:04:51 +0100 Alex <alex@×××××××.de> wrote: |
21 |
> |
22 |
> |
23 |
>> i would suggest an alias for this -> |
24 |
>> http://httpd.apache.org/docs/2.0/mod/mod_alias.html#alias |
25 |
>> |
26 |
>> Aliases werde made for this kind of problem ( data's were not in the |
27 |
>> documentroot) |
28 |
>> |
29 |
> |
30 |
> Yep, but they're not made for *this* exact kind of problem: Here, the |
31 |
> file isn't even in the accessible filesystem namespace. |
32 |
> |
33 |
> BTW, I've always found it easier to manage a bunch of symlinks instead |
34 |
> of numerous .htaccess files. But again, in the OP's case neither works. |
35 |
> |
36 |
> -hwh |
37 |
> |
38 |
-- |
39 |
gentoo-user@g.o mailing list |