From: Johannes Sixt <j6t@kdbg.org>
To: Jeff King <peff@peff.net>
Cc: Ian Kumlien <pomac@vapor.com>, git@vger.kernel.org
Subject: Re: git-daemon: needs /root/.config/git/config?
Date: Tue, 04 Jun 2013 21:05:44 +0200 [thread overview]
Message-ID: <51AE3A88.2080203@kdbg.org> (raw)
In-Reply-To: <20130604160815.GB15953@sigill.intra.peff.net>
Am 04.06.2013 18:08, schrieb Jeff King:
> Older versions of git silently ignored errors reading config files, but
> it was tightened in v1.8.1.1, as there can be quite serious implications
> to failing to read expected config (e.g., imagine transfer.fsckobjects,
> or receive.deny* is ignored).
>
> However, since changing user id and leaving $HOME is so common, there is
> a patch under consideration to loosen the check only for the case of
> EACCES on files in $HOME. That commit is 4698c8f (config: allow
> inaccessible configuration under $HOME, 2013-04-12); it's not yet in any
> released version of git, though.
>
> In the meantime, the suggested workaround is to set $HOME for the
> git-daemon user, rather than loosening /root.
I've a PHP script in ~/public_html that runs git. Without the mentioned
patch, the script bails out due to this error. This time it's Apache
that gets me into trouble because at the time the PHP script and git
run, $HOME is still /root, but the user identity is not root anymore.
The patch is direly needed; without it, I need to use 'env
HOME=/home/j6t /usr/local/bin/git' in my script.
-- Hannes
next prev parent reply other threads:[~2013-06-04 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 14:13 git-daemon: needs /root/.config/git/config? Ian Kumlien
2013-06-04 16:08 ` Jeff King
2013-06-04 19:05 ` Johannes Sixt [this message]
2013-06-04 19:10 ` Jonathan Nieder
2013-06-04 19:20 ` Junio C Hamano
2013-06-04 21:06 ` Jeff King
2013-06-04 21:24 ` Junio C Hamano
2013-06-05 11:19 ` Ian Kumlien
2013-06-05 11:43 ` Andreas Krey
2013-06-05 15:43 ` Jeff King
2013-06-09 12:47 ` Bernhard R. Link
2013-06-10 12:06 ` Ian Kumlien
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=51AE3A88.2080203@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=pomac@vapor.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).