How to prevent code from leaking outside work?
Posted
by
AeroCross
on Programmers
See other posts from Programmers
or by AeroCross
Published on 2012-10-17T16:25:29Z
Indexed on
2012/10/17
17:19 UTC
Read the original article
Hit count: 262
source-code
|closed-source
I'm working on an institution that has a really strong sense of "possession" - each line of software we write should be only ours. Ironically, I'm the only programmer (ATM), but we're planning in hiring others.
Since my bosses wouldn't count the new programmers as people they can trust, they have an issue with the copies of the source code. We use Git, so they would have a entire copy of each of the projects they work on, when they clone the repository.
We can restrict access to them to a single key with Gitolite and bind that to their PC's, but they can copy those keys to another computer and they would have the repository access in another PC. Also (and the most obvious method) they could just upload the files somewhere else, add another remote, or just copy the files to an USB drive.
Is there any (perhaps clever) way to prevent events like these?
© Programmers or respective owner