Re: aname_to_locaname vs gssapi svc/host.domain.org@REALM
Russ Allbery <[email protected]>
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Organization | The Eyrie |
| Message-ID | <[email protected]> |
[email protected] writes: > On Wed, Oct 26, 2011 at 06:58:43PM -0700, Russ Allbery wrote: >> No, that is a rare case for Apache, actually. It's only really true in >> the old world of static web pages, which is vanishing. You almost >> never want the user of a PHP application to have access to the PHP >> source, which is what's stored in the shared file system. > Unfortunately, to be able to fulfil the request of a user, Apache has to > read the PHP code and the (possibly user-specific) data which are the > ground for the page to be dynamically generated. Correct. And often that's data that the user should not have access to, and is stored in a network file system. > It is Apache's task to isolate its raw data from the generated one (this > function was less evident with static pages), but this is not controlled > by the raw data access privileges, which we were concerned about here. The raw data access privileges have to not permit access by the user. Therefore, Apache is not a proxy for the user and has to have different credentials than the user has, which refutes the original point. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>