git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: git@vger.kernel.org
Subject: Question about scm security holes
Date: Thu, 04 Mar 2010 12:09:41 -0800	[thread overview]
Message-ID: <hmp427$d6h$1@dough.gmane.org> (raw)

I just saw this article about the "google hackers" exploiting weaknesses in scms,
Perforce in particular:

http://www.wired.com/threatlevel/2010/03/source-code-hacks/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+wired%2Findex+%28Wired%3A+Index+3+%28Top+Stories+2%29%29

I guess google didn't take Linus's advice to dump Perforce :)

I can't tell from the article if Perforce is any worse than any other scm for
security holes, in fact it seems to imply that others haven't been tested in
the same way.

Just curious if anyone here has any thoughts about how the article may or may
not have any relevance for git (git being the scm I use most, by far, which is
the reason I'm interested).

Thanks

             reply	other threads:[~2010-03-05  1:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 20:09 walt [this message]
2010-03-05  2:03 ` Question about scm security holes 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
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='hmp427$d6h$1@dough.gmane.org' \
    --to=w41ter@gmail.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. 
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).