diff options
author | Jonathan Nieder <jrnieder@gmail.com> | 2012-10-14 01:46:00 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2012-10-14 10:14:52 -0700 |
commit | 8f2bbe452e2c2917ec3c9a5d1593f26908cab83b (patch) | |
tree | 72654db66b0202f3b1d2c72b6fc0e6b8ddf904a9 /t/t4105-apply-fuzz.sh | |
parent | doc: advertise GIT_CONFIG_NOSYSTEM (diff) | |
download | tgif-8f2bbe452e2c2917ec3c9a5d1593f26908cab83b.tar.xz |
config: exit on error accessing any config file
There is convenience in warning and moving on when somebody has a
bogus permissions on /etc/gitconfig and cannot do anything about it.
But the cost in predictability and security is too high --- when
unreadable config files are skipped, it means an I/O error or
permissions problem causes important configuration to be bypassed.
For example, servers may depend on /etc/gitconfig to enforce security
policy (setting transfer.fsckObjects or receive.deny*). Best to
always error out when encountering trouble accessing a config file.
This may add inconvenience in some cases:
1. You are inspecting somebody else's repo, and you do not have
access to their .git/config file. Git typically dies in this
case already since we cannot read core.repositoryFormatVersion,
so the change should not be too noticeable.
2. You have used "sudo -u" or a similar tool to switch uid, and your
environment still points Git at your original user's global
config, which is not readable. In this case people really would
be inconvenienced (they would rather see the harmless warning and
continue the operation) but they can work around it by setting
HOME appropriately after switching uids.
3. You do not have access to /etc/gitconfig due to a broken setup.
In this case, erroring out is a good way to put pressure on the
sysadmin to fix the setup. While they wait for a reply, users
can set GIT_CONFIG_NOSYSTEM to true to keep Git working without
complaint.
After this patch, errors accessing the repository-local and systemwide
config files and files requested in include directives cause Git to
exit, just like errors accessing ~/.gitconfig.
Explained-by: Jeff King <peff@peff.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Acked-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4105-apply-fuzz.sh')
0 files changed, 0 insertions, 0 deletions