blob: e3552c8a350cc894b44b912e714800c805ad4069 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1UMa4s-000195-42
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Apr 2013 08:26:54 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.180 as permitted sender)
client-ip=209.85.217.180; envelope-from=melvincarvalho@gmail.com;
helo=mail-lb0-f180.google.com;
Received: from mail-lb0-f180.google.com ([209.85.217.180])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UMa4m-0007Jq-Fu
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Apr 2013 08:26:54 +0000
Received: by mail-lb0-f180.google.com with SMTP id t11so1721512lbi.39
for <bitcoin-development@lists.sourceforge.net>;
Mon, 01 Apr 2013 01:26:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.87.243 with SMTP id bb19mr5222330lab.12.1364804801665;
Mon, 01 Apr 2013 01:26:41 -0700 (PDT)
Received: by 10.112.143.38 with HTTP; Mon, 1 Apr 2013 01:26:41 -0700 (PDT)
Date: Mon, 1 Apr 2013 10:26:41 +0200
Message-ID: <CAKaEYhK5ZzP8scbhyzkEU+WdWjwMBDzkgF+SrC-Mdjgo9G9RnA@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c3537a641fec04d94861ac
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(melvincarvalho[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UMa4m-0007Jq-Fu
Subject: [Bitcoin-development] bitcoin pull requests
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 08:26:54 -0000
--001a11c3537a641fec04d94861ac
Content-Type: text/plain; charset=ISO-8859-1
I was just looking at:
https://bitcointalk.org/index.php?topic=4571.0
I'm just curious if there is a possible attack vector here based on the
fact that git uses the relatively week SHA1
Could a seemingly innocuous pull request generate another file with a
backdoor/nonce combination that slips under the radar?
Apologies if this has come up before ...
--001a11c3537a641fec04d94861ac
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>I was just looking at:<br><br><a href=3D"ht=
tps://bitcointalk.org/index.php?topic=3D4571.0">https://bitcointalk.org/ind=
ex.php?topic=3D4571.0</a><br><br></div>I'm just curious if there is a p=
ossible attack vector here based on the fact that git uses the relatively w=
eek SHA1<br>
<br></div>Could a seemingly innocuous pull request generate another file wi=
th a backdoor/nonce combination that slips under the radar?<br><br></div>Ap=
ologies if this has come up before ...<br></div>
--001a11c3537a641fec04d94861ac--
|
