git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: walt <w41ter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Question about scm security holes
Date: Thu, 4 Mar 2010 22:28:38 -0500	[thread overview]
Message-ID: <32541b131003041928m50aee3d0jcde58f3f4ff63a8b@mail.gmail.com> (raw)
In-Reply-To: <4B907884.5080501@gmail.com>

On Thu, Mar 4, 2010 at 10:20 PM, walt <w41ter@gmail.com> wrote:
> On 03/04/2010 06:03 PM, Avery Pennarun wrote:
>> ...you can create a commit with
>> whatever committer/author names you want and then push them in.
>> Commits aren't GPG-signed, only tags are, so there are lots of ways to
>> forge a commit from someone else and mess up the audit log...
>
> Thanks, that's the kind of reply I was hoping for.  Do you think there
> should be a way to sign the commits themselves, at least as an option?
>
> I certainly wouldn't bother, but OTOH nobody wants to steal my code :-/

The whole thing is a bit overblown.  One of my friends once took me on
a tour of Microsoft on a weekend.  The place was mostly deserted, but
tons of developers left their workstations unlocked overnight, and
everyone had a private office.  And with tens of thousands of
developers on the campus, nobody would know if you're supposed to be
there or not.

It would have been easy to walk off with the source code to Windows
from one of those workstations.  The fact is, nobody really *wants*
the source code to Windows, except probably to look at it and be
horrified.

What would you do if you stole the source code to Adobe's flash
player?  It's illegal (in the U.S. anyway) to reverse engineer it and
it's illegal to steal it, so you're on the wrong side of the law no
matter how you pretend you managed to figure out a way around their
DRM or whatever.

People describe source code as a company's "crown jewels," but that's
a bit of a joke.  I can barely get our interns to figure out how to
compile and understand our code.  Expecting a thief to do it, with
nothing but a raw repo and hundreds of gigabytes of crap, is pure
paranoia.

Sneaking in patches?  Yeah, watch out for that.  But you should be
reviewing patch changelogs anyway.  At least git prevents people from
*retroactively* changing stuff; they can only add patches on top, so
it's easy to review after a break-in.

Have fun,

Avery

  reply	other threads:[~2010-03-05  3:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 20:09 Question about scm security holes walt
2010-03-05  2:03 ` Avery Pennarun
2010-03-05  3:00   ` John Tapsell
2010-03-05  3:19     ` Avery Pennarun
2010-03-05  4:07       ` John Tapsell
2010-03-05  3:20   ` walt
2010-03-05  3:28     ` Avery Pennarun [this message]
2010-03-05  7:36   ` Andreas Krey
2010-03-05  9:25   ` Johannes Schindelin
2010-03-05 10:49     ` Jakub Narebski
2010-03-05 18:22     ` Avery Pennarun
2010-03-05 22:33       ` Johannes Schindelin
2010-03-05 17:47 ` Daniel Barkalow

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32541b131003041928m50aee3d0jcde58f3f4ff63a8b@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=w41ter@gmail.com \
    /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.
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 NNTP newsgroup(s).