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

Re: Repository Code Security (Plan Text)

From
KKKonstantin Khomoutov <kostix+git@007spb.ru>
Date
Jun 24, 2015, 18:31 UTC
Message-ID
<20150624213111.61ce6933040bbb7220d5903c@domain007.com>
In-Reply-To
<BLUPR0701MB19693B73E05DF433C6B70182D7AF0@BLUPR0701MB1969.namprd07.prod.outlook.com>

On Wed, 24 Jun 2015 18:18:00 +0000 BGaudreault Brian <BGaudreault@edrnet.com> wrote:

> If someone downloads code to their notebook PC and leaves the
> company, what protection do we have against them not being able to
> access the local code copy anymore?

What do you mean by "local code"? That one which is on the notebook? Then you can do literally nothing except for not allowing cloning your Git repositories onto random computers in the first place.

If you instead mean the copy of code available in the repositories hosted in your enterprise then all you need to do is to somehow terminate the access of that employee who's left to those repositories. (This assumes they're accessible from the outside; if they aren't, the problem simply do not exist.)

Previous: BGaudreault BrianNext: BGaudreault Brian
Message 2 of 9 in “Repository Code Security (Plan Text)”
  1. BGaudreault BrianJun 24, 2015
  2. Konstantin KhomoutovJun 24, 2015
  3. BGaudreault BrianJun 24, 2015
  4. David LangJun 24, 2015
  5. BGaudreault BrianJun 24, 2015
  6. David TurnerJun 24, 2015
  7. BGaudreault BrianJun 24, 2015
  8. David LangJun 24, 2015
  9. David TurnerJun 24, 2015

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.