git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git and securing a repository

From
GGGonzalo Garramuño <ggarra@advancedsl.com.ar>
Date
Jan 3, 2008, 06:08 UTC
Message-ID
<477C7BF8.2090406@advancedsl.com.ar>
In-Reply-To
<20080103044552.GB24004@spearce.org>
Shawn O. Pearce wrote:
Show 6 quoted lines
> 
> Its a distributed version control system.  All peers are equal.
> Most security in Git is handled by only pulling from sources you
> trust, and never allowing someone to push stuff into a repository
> you own.
>

Regarding that... is there a way to control the umask of a git clone independent of the actual umask of the user or directories inside the repository? Ideally, on the server side?

That is, for sensitive repositories, I would like "git clone" to always clone that repository with 0700 permissions, so that the silly mistake of cloning a sensitive repository into a public directory and forgetting to restrict its permissions can be avoided completely.

-- 
Gonzalo Garramuño
ggarra@advancedsl.com.ar

AMD4400 - ASUS48N-E
GeForce7300GT
Xubuntu Gutsy
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 11 of 18 in “Git and securing a repository”
  1. Gonzalo GarramuñoJan 2, 2008
  2. Felipe BalbiJan 2, 2008
  3. Gonzalo GarramuñoJan 2, 2008
  4. David SymondsJan 2, 2008
  5. Gonzalo GarramuñoJan 2, 2008
  6. Jakub NarebskiJan 2, 2008
  7. Shawn O. PearceJan 3, 2008
  8. Bruno Cesar RibasJan 3, 2008
  9. Gonzalo GarramuñoJan 3, 2008
  10. Shawn O. PearceJan 3, 2008
  11. Gonzalo GarramuñoJan 3, 2008
  12. Shawn O. PearceJan 3, 2008
  13. Jakub NarebskiJan 3, 2008
  14. Junio C HamanoJan 3, 2008
  15. Jan HudecJan 2, 2008
  16. Gregory JefferisJan 2, 2008
  17. Linus TorvaldsJan 2, 2008
  18. Daniel BarkalowJan 2, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.