From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-receive-pack needs to set umask(2)
Date: Mon, 29 May 2006 12:03:40 -0400 [thread overview]
Message-ID: <18609.1148918620@sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from Petr Baudis <pasky@ucw.cz> of "Mon, 29 May 2006 00:06:28 +0200." <20060528220628.GE10488@pasky.or.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Petr" == Petr Baudis <pasky@ucw.cz> writes:
Petr> The object database is considered "append-only" unless you do
Petr> git-prune (and you should better not let anyone do that), thus
Petr> it's enough if you set all directories group-writable. Other
Exactly, you have to do that. And only the owner can change the modes,
thus, unless all users have their umask set up right, someone gets toasted.
Since the directories are created on the fly, they need to be created
with the right permissions.
Petr> than access the object database, the users probably only want
Petr> to update the refs - the solution is to make refs/heads/ and
Petr> refs/tags/ group-writable and setgid. This is also what
Petr> git-init-db --shared (or tools like cg-admin-setuprepo) should
Petr> already set up for you.
Petr> So, what did break?
Never heard of "git-init-db --shared".
> A shared repository allows users belonging to the same group to push
> into that repository. When specifying `--shared` the config variable
> "core.sharedRepository" is set to 'true' so that directories under
> `$GIT_DIR` are made group writable (and g+sx, since the git group may
> be not the primary group of all users).
That would seem to be the right thing.
Seems it was added in December.
- --
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
"The Microsoft _Get the Facts CD_ does not work on Linux." - orospakr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Finger me for keys
iQEVAwUBRHsbW4CLcPvd0N1lAQKa/gf+MF93+zbNnmqpysWMmYPVhW6HvU6XFyCQ
KyTfA7dxVX3tS9coSAcT73IX659umMz1MkyG7YR4ISFLlhLmdthq6l/ETueTZPVw
SgTSEU9TT2sM+gjtzy6v1wGQJAXJxYw6kJgKOFgCfyIPsb7EZWyQBmZLiNU0omnv
gkV8Ja5pJPTNHcinzzNyg8LIm0j55cS9OG9XQrXm46q+9OX+y39BoxGnz3Guzmry
yzfx1ipDuW54QCzKRyBpwt7/1LBfk/eJAH0wP9IAA4qz39+OA2yz8fTMvHDB1a6V
H18SkBENb6ZllGovu60IUgJCKy2sizGkBGUax9ec2ByAzHL1al3W3g==
=arDu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-05-29 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 21:31 [PATCH] git-receive-pack needs to set umask(2) Michael Richardson
2006-05-28 22:00 ` Jakub Narebski
2006-05-29 7:13 ` Johannes Schindelin
2006-05-29 11:28 ` Salikh Zakirov
2006-05-29 11:33 ` Shawn Pearce
2006-05-29 17:00 ` Linus Torvalds
2006-05-29 21:28 ` Alex Riesen
2006-05-29 21:50 ` Johannes Schindelin
2006-05-28 22:06 ` Petr Baudis
2006-05-29 16:03 ` Michael Richardson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 12:07 Zakirov, Salikh
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=18609.1148918620@sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.