From: Martin Langhoff <martin.langhoff@gmail.com>
To: Jeff King <peff@peff.net>
Cc: William DiNoia <william.dinoia@mac.com>, git@vger.kernel.org
Subject: Re: git for local web development
Date: Fri, 17 Apr 2009 20:48:13 +0200 [thread overview]
Message-ID: <46a038f90904171148xefb2085yc47e58c62cd3bbaf@mail.gmail.com> (raw)
In-Reply-To: <20090417183046.GB30240@coredump.intra.peff.net>
On Fri, Apr 17, 2009 at 8:30 PM, Jeff King <peff@peff.net> wrote:
> repo and working tree are not owned by "william"? As long as www-data,
> presumably the webserver could still serve it.
Also, as long as they are owned by www-data, the setup is more
vulnerable to security problems.
Files served by Apache (or any other webserver) should _not_ be owned
by the same user that the webserver runs under. The www-data ownership
is exclusively for files that you expect the webserver to be able to
_modify_: files uploaded by users, session data files, sqlite
databases and such.
You don't really want your webserver changing executable files such as PHP.
It is a valid thing to create a user to own those files, and in
servers where a team was maintaining the code, we have often used
'www-code'.
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-04-17 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 23:04 git for local web development William DiNoia
2009-04-17 11:59 ` Jeff King
2009-04-17 15:44 ` William DiNoia
2009-04-17 18:30 ` Jeff King
2009-04-17 18:48 ` Martin Langhoff [this message]
2009-04-17 22:00 ` William DiNoia
-- strict thread matches above, loose matches on Subject: below --
2009-04-17 0:56 William DiNoia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f90904171148xefb2085yc47e58c62cd3bbaf@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=william.dinoia@mac.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).