From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: BGaudreault Brian <BGaudreault@edrnet.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Repository Code Security (Plan Text)
Date: Wed, 24 Jun 2015 21:31:11 +0300 [thread overview]
Message-ID: <20150624213111.61ce6933040bbb7220d5903c@domain007.com> (raw)
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.)
next prev parent reply other threads:[~2015-06-24 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 18:18 Repository Code Security (Plan Text) BGaudreault Brian
2015-06-24 18:31 ` Konstantin Khomoutov [this message]
2015-06-24 18:59 ` BGaudreault Brian
2015-06-24 19:20 ` David Lang
2015-06-24 19:53 ` BGaudreault Brian
2015-06-24 20:00 ` David Turner
2015-06-24 20:17 ` BGaudreault Brian
2015-06-24 20:10 ` David Lang
2015-06-24 19:21 ` David Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150624213111.61ce6933040bbb7220d5903c@domain007.com \
--to=kostix+git@007spb.ru \
--cc=BGaudreault@edrnet.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).