blob: d1bb0808192ce8ca5951347d53c39fd980857de7 (
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <nanotube@gmail.com>) id 1R7D8x-0005Eu-KS
for bitcoin-development@lists.sourceforge.net;
Fri, 23 Sep 2011 21:18:47 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.47 as permitted sender)
client-ip=209.85.214.47; envelope-from=nanotube@gmail.com;
helo=mail-bw0-f47.google.com;
Received: from mail-bw0-f47.google.com ([209.85.214.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R7D8w-0003SD-TC
for bitcoin-development@lists.sourceforge.net;
Fri, 23 Sep 2011 21:18:47 +0000
Received: by bke11 with SMTP id 11so5558317bke.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 23 Sep 2011 14:18:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.135.70 with SMTP id m6mr1748517bkt.165.1316812720423; Fri,
23 Sep 2011 14:18:40 -0700 (PDT)
Received: by 10.204.78.14 with HTTP; Fri, 23 Sep 2011 14:18:40 -0700 (PDT)
In-Reply-To: <j5ineh$g3a$1@dough.gmane.org>
References: <CABsx9T1Z5NPbDfPcRKvZ8f+e05RMQVhm2WQyeFNti_w5nk4D7Q@mail.gmail.com>
<j5ineh$g3a$1@dough.gmane.org>
Date: Fri, 23 Sep 2011 17:18:40 -0400
Message-ID: <CAHY2ayAwG2GiDR7Cn-CTryXzFLXd=T2Nx=VCVbj9awrB6TDxDg@mail.gmail.com>
From: Daniel F <nanotube@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.2 (-)
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
(nanotube[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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
0.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R7D8w-0003SD-TC
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin 0.4.0 released
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: Fri, 23 Sep 2011 21:18:47 -0000
> Can you post secure file checksums somewhere, preferably not on Sourceforge?
as long as it's gpg-signed, what's the difference where it is posted?
|
