On 17 Apr 2008, at 21:22, Stefan de Konink wrote:
> On Thu, 17 Apr 2008, A.D.F. wrote:
>
>> So, the final solution could be:
>>
>> [ ] enable readability bit filters (only legacy systems, NO ACLs)
>> NOTE: if enabled, at least 1 readability bit (user,group,world)
>> has to be set in order to allow access to static files
>>
>> [ ] filter to require "world bit" readability
>>
>> [ ] filter to require "group bit" readability
>
> [ ] enable a message if Cherokee runs as root
I would go for:
- Warn user if cherokee runs as root:
This is the source of the problem, the user should know about this
and be aware of the misconfiguration.
- Let the OS do its job and take care of the permissions, and
therefore return errors only when the server cannot access the
resource. The idea is to be consistent with the system, if programs
run by root have super-powers, there is no reason to treat Cherokee
differently.
If we went the let's-try-to-make-root-safe way, we would have to fix a
bunch of additional issues. For instance, it wouldn't make sense to
chroot the server if it runs as root, but again, that is not a problem
that we ought to face.
--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
