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
|
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 1Tdfmo-0004VB-U2
for bitcoin-development@lists.sourceforge.net;
Wed, 28 Nov 2012 11:26:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.175 as permitted sender)
client-ip=209.85.214.175; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f175.google.com;
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Tdfmj-0005nj-DJ
for bitcoin-development@lists.sourceforge.net;
Wed, 28 Nov 2012 11:26:38 +0000
Received: by mail-ob0-f175.google.com with SMTP id vb8so12421066obc.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 28 Nov 2012 03:26:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.156.99 with SMTP id wd3mr2812006obb.15.1354101988048; Wed,
28 Nov 2012 03:26:28 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.128.139 with HTTP; Wed, 28 Nov 2012 03:26:27 -0800 (PST)
In-Reply-To: <CA+8xBpf6kGYPiG7HvyG+2pCAcsBN8_T4MVFnW+rwvE68BiZJsQ@mail.gmail.com>
References: <CA+8xBpf6kGYPiG7HvyG+2pCAcsBN8_T4MVFnW+rwvE68BiZJsQ@mail.gmail.com>
Date: Wed, 28 Nov 2012 12:26:27 +0100
X-Google-Sender-Auth: TVo9qJwlHz_qH1F9Nm8W793RuvY
Message-ID: <CANEZrP2X5zt3qbiqq6AyxM67Rn8woji9j1gEAaatMm0EotKstw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.4 (-)
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.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Tdfmj-0005nj-DJ
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [ANNOUNCE] picocoin and libccoin --
C-based bitcoin library and client
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: Wed, 28 Nov 2012 11:26:39 -0000
Cool, will check it out soon.
> libccoin should work on Windows. picocoin will work on Windows,
> but be a bit less secure than other platforms due to lack of fork.
FYI, Windows has quite good sandboxing support. You could implement
the same thing later with Win32 if you want.
|
