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

Re: Question about scm security holes

From
Andreas Krey <a.krey@gmx.de>
Date
Mar 5, 2010, 07:36 UTC
Message-ID
<20100305073642.GA16131@inner.home.ulmdo.de>
In-Reply-To
<32541b131003041803q9abf6baq4cf9ffcca990b51c@mail.gmail.com>

On Thu, 04 Mar 2010 21:03:08 +0000, Avery Pennarun wrote: ...

> where every single developer workstation has a complete copy of the
> entire project history anyway.

It's the point of a dev workstation to have access to the code, so McAfees whining about SCMs letting that happen is moot.

What would be helping here is a separation between internet-facing and local work into separate machines.

> least.  Traceable, not so much, because you can create a commit with
> whatever committer/author names you want and then push them in.

You can still log who pushed what into your blessed repo, and hold that person accountable.

Andreas
Previous: Avery PennarunNext: Johannes Schindelin
Message 8 of 13 in “Question about scm security holes”
  1. waltMar 4, 2010
  2. Avery PennarunMar 5, 2010
  3. John TapsellMar 5, 2010
  4. Avery PennarunMar 5, 2010
  5. John TapsellMar 5, 2010
  6. waltMar 5, 2010
  7. Avery PennarunMar 5, 2010
  8. Andreas KreyMar 5, 2010
  9. Johannes SchindelinMar 5, 2010
  10. Jakub NarebskiMar 5, 2010
  11. Avery PennarunMar 5, 2010
  12. Johannes SchindelinMar 5, 2010
  13. Daniel BarkalowMar 5, 2010

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.