From: Avery Pennarun <apenwarr@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Question about scm security holes
Date: Thu, 4 Mar 2010 22:19:13 -0500 [thread overview]
Message-ID: <32541b131003041919u6a477b46s447a6aeb18f3b393@mail.gmail.com> (raw)
In-Reply-To: <43d8ce651003041900x66000be4s9a15ab0cde3a0fe7@mail.gmail.com>
On Thu, Mar 4, 2010 at 10:00 PM, John Tapsell <johnflux@gmail.com> wrote:
> On 5 March 2010 02:03, Avery Pennarun <apenwarr@gmail.com> wrote:
>> modified code would be a little more interesting. git makes this sort
>> of thing pretty much impossible to do without it being *noticeable* at
>> least. Traceable, not so much, because you can create a commit with
>> whatever committer/author names you want and then push them in.
>
> Which is why you simply record the username of whoever pushed them in.
> This is what gitorious.org does etc.
Not bad, but it's still very hard to trace properly. Imagine I pull
from a peer, then push my combined branch into the central repo.
It'll say I'm pushing in patches from me *and* my friend. Did I forge
them or are they real?
Avery
next prev parent reply other threads:[~2010-03-05 3:19 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 [this message]
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=32541b131003041919u6a477b46s447a6aeb18f3b393@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@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).