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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1QbRu2-0007bE-GH
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 06:36:06 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com;
helo=mail-vw0-f47.google.com;
Received: from mail-vw0-f47.google.com ([209.85.212.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QbRu1-00049J-EU
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Jun 2011 06:36:06 +0000
Received: by vws2 with SMTP id 2so5751019vws.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 27 Jun 2011 23:36:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.74.234 with SMTP id x10mr9803925vdv.18.1309242959870; Mon,
27 Jun 2011 23:35:59 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.52.169.40 with HTTP; Mon, 27 Jun 2011 23:35:59 -0700 (PDT)
In-Reply-To: <C9421AA2-D741-4989-9DA8-395D1F532F52@jrbobdobbs.org>
References: <D024B465-AD6C-4AAD-A07F-956223929B6F@jrbobdobbs.org>
<C9421AA2-D741-4989-9DA8-395D1F532F52@jrbobdobbs.org>
Date: Tue, 28 Jun 2011 08:35:59 +0200
X-Google-Sender-Auth: Aolqlw9CZpuu7afcBYCMjfj4_qY
Message-ID: <BANLkTi=RASna0vQ0bYGc8ApWC++PsNqSAg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Doug Huff <dhuff@jrbobdobbs.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.3 (-)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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
0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QbRu1-00049J-EU
Cc: Bitcoin Dev Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Live mtgox.com trade matching bug.
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: Tue, 28 Jun 2011 06:36:06 -0000
Hi Doug,
Could we keep the Mt Gox related stuff off bitcoin-development please?
It's not related to the core software.
On Tue, Jun 28, 2011 at 4:48 AM, Doug Huff <dhuff@jrbobdobbs.org> wrote:
>
>
> Begin forwarded message:
>
>> From: Doug Huff <mith@jrbobdobbs.org>
>> Date: June 27, 2011 9:46:13 PM CDT
>> To: full-disclosure@lists.grok.org.uk, "Mt.Gox" <info@mtgox.com>
>> Cc: Bitcoin Dev Development <bitcoin-development@lists.sourceforge.net>
>> Subject: Live mtgox.com trade matching bug.
>>
>> Step 1: Have USD available for spending on mtgox.com.
>> Step 2: Put in a buy order large enough to drain your account. Low enoug=
h under the current trading price that it will not execute immediately.
>> Step 3: Withdraw all USD funds.
>> Step 4: Wait for market to fall enough to meet your order.
>> Step 5: ...(self explanatory)...
>>
>> There's a bit of luck in being able to take advantage, obviously.
>>
>> I would suggest you take the site down asap until this is corrected or p=
ublicly show how this order will never execute:
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Welcome <username removed> 0.00000000 =E0=B8=BFTC 424.44901
>> Buying =C2=A0138468.901 =C2=A00.01 =C2=A0Active =C2=A01384.69 =C2=A006/2=
6 15:27 =C2=A0cancel
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> I cannot guarantee this order will execute but from everything I've obse=
rved about the new trade matching code I have no reason to believe it will =
not.
>>
>> At the very least this could be used to influence market conditions if i=
t is only a display bug.
>>
>> --
>> Douglas Huff
>>
>>
>
> --
> Doug Huff
>
>
>
> -------------------------------------------------------------------------=
-----
> All of the data generated in your IT infrastructure is seriously valuable=
.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
|
