Subject: Re: Repository Code Security (Plan Text)

From: David Turner <[email-masked]>
Date: Wed, 24 Jun 2015 15:21:12 -0400

What most companies do is this: they issue their employees computers,
and then when the employee leaves, they take the computers away.  Of
course, someone could have copied the code before leaving the company.
The typical remedy for this is a contract saying "don't do that".  But I
guess some companies just go straight to the FBI see e.g.:
https://en.wikipedia.org/wiki/Sergey_Aleynikov

There is no technological solution that will prevent someone from
accessing something that lives on their own computer (just ask the movie
and music industries, which tried to find one for about twenty years).  

On Wed, 2015-06-24 at 18:59 +0000, BGaudreault Brian wrote:
> Thanks.  Yes, I meant that "local code" is code pulled down to a person's PC, so we don't want them to leave the company with access to this code.  So we can only prevent this scenario by running GitLab in our environment instead of running GitHub in the cloud?  Would removing a GitHub account from the GitHub repository prevent them from accessing the code on their PC?
> 
> How do you prevent private GitHub repositories from being pulled down to unauthorized PCs?
> 
> Thanks,
> Brian
> 
> -----Original Message-----
> From: Konstantin Khomoutov [mailto:[email-masked]] 
> Sent: Wednesday, June 24, 2015 2:31 PM
> To: BGaudreault Brian
> Cc: [email-masked]
> Subject: Re: Repository Code Security (Plan Text)
> 
> On Wed, 24 Jun 2015 18:18:00 +0000
> BGaudreault Brian <[email-masked]> 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.)
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to [email-masked]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html