{"thread":{"id":"17446","subject":"Security and permissions in git","startedAt":"2009-01-29T20:34:38Z","lastAt":"2009-01-29T23:23:58Z","messageCount":3,"participants":["Jay Renbaum","Daniel Barkalow","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"102500","messageId":"loom.20090129T203050-865@post.gmane.org","threadId":"17446","inReplyTo":null,"subject":"Security and permissions in git","fromName":"Jay Renbaum","fromEmail":"jrenbaum@hcrest.com","sentAt":"2009-01-29T20:34:38Z","receivedAt":"2009-01-29T20:34:38Z","isPatch":false,"sender":{"key":"jrenbaum@hcrest.com","avatar":null},"body":"When setting up a public repository is there a way to control who has access \nto various directories within the repository or is everything equal once you \nare in?\n"},{"id":"102507","messageId":"alpine.LNX.1.00.0901291645300.19665@iabervon.org","threadId":"17446","inReplyTo":"loom.20090129T203050-865@post.gmane.org","subject":"Re: Security and permissions in git","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2009-01-29T22:13:41Z","receivedAt":"2009-01-29T22:13:41Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Thu, 29 Jan 2009, Jay Renbaum wrote:\n\n> When setting up a public repository is there a way to control who has access \n> to various directories within the repository or is everything equal once you \n> are in?\n\nEvery commit contains a version of the complete contents, so people have \nto be able to read the contents of all directories and write some \ndirectory contents. However, you can prohibit users from pushing content \nto the repository unless particular directories (or files) match what's \nthere already. This is generally what people want when they have this \nrequirement.\n\nIt's also possible to use submodules to have a project contain parts that \nsome users don't have any access to, while still being able to produce \ncommits to the main project (in combination with the above check so that \ntry can't replace the submodule entirely with content they do have access \nto, or submodule commits they've seen referenced previously)\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"102525","messageId":"20090129232358.GA12941@coredump.intra.peff.net","threadId":"17446","inReplyTo":"alpine.LNX.1.00.0901291645300.19665@iabervon.org","subject":"Re: Security and permissions in git","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-29T23:23:58Z","receivedAt":"2009-01-29T23:23:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Jan 29, 2009 at 05:13:41PM -0500, Daniel Barkalow wrote:\n\n> Every commit contains a version of the complete contents, so people have \n> to be able to read the contents of all directories and write some \n> directory contents. However, you can prohibit users from pushing content \n> to the repository unless particular directories (or files) match what's \n> there already. This is generally what people want when they have this \n> requirement.\n\nIf this is what you want, see Shawn's contrib/hooks/update-paranoid,\nwhich lets you specify ACLs in the config.\n\n-Peff\n"}]}