blob: 5fb6c2b99f2bc020c28cdfcc25ab75ef2ec165f2 (
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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1RpO2k-0006f8-DE
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Jan 2012 17:50:58 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.41 as permitted sender)
client-ip=74.125.82.41; envelope-from=mh.in.england@gmail.com;
helo=mail-ww0-f41.google.com;
Received: from mail-ww0-f41.google.com ([74.125.82.41])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RpO2j-0000Fl-JK
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Jan 2012 17:50:58 +0000
Received: by wgbdt11 with SMTP id dt11so3006491wgb.4
for <bitcoin-development@lists.sourceforge.net>;
Mon, 23 Jan 2012 09:50:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.107.99 with SMTP id hb3mr15067194wib.0.1327341051533; Mon,
23 Jan 2012 09:50:51 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.216.29.73 with HTTP; Mon, 23 Jan 2012 09:50:51 -0800 (PST)
In-Reply-To: <4F1C0CAB.4000905@netmind.hu>
References: <4F1C0CAB.4000905@netmind.hu>
Date: Mon, 23 Jan 2012 18:50:51 +0100
X-Google-Sender-Auth: TQpIN23L1cGU7pFar79LAQO8izs
Message-ID: <CANEZrP31-7gGDxze11QHBpt0sG3M5A6yviM++7RM63fRHzUwdA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?Q?Brautigam_R=C3=B3bert?= <robert.brautigam@netmind.hu>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.0 (-)
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.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RpO2j-0000Fl-JK
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] ECC Signature Issue
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, 23 Jan 2012 17:50:58 -0000
> I double checked that the official (C++) client is indeed successful
> here. Oddly enough the bitcoinj implementation also seems to fail to
> verify this transaction, which seems to point in the direction of
> BouncyCastle (which we both use).
BitCoinJ does not verify signatures (it is an SPV implementation), so
I'm not sure what you mean by this. Are you using old code? There used
to be some stuff that checked signatures but it was removed some time
ago.
|
