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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1V1jXb-0002ap-HO
for bitcoin-development@lists.sourceforge.net;
Tue, 23 Jul 2013 20:50:39 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.44 as permitted sender)
client-ip=209.85.215.44; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f44.google.com;
Received: from mail-la0-f44.google.com ([209.85.215.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V1jXX-0000bt-OH
for bitcoin-development@lists.sourceforge.net;
Tue, 23 Jul 2013 20:50:39 +0000
Received: by mail-la0-f44.google.com with SMTP id er20so6642945lab.3
for <bitcoin-development@lists.sourceforge.net>;
Tue, 23 Jul 2013 13:50:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.18.165 with SMTP id x5mr9998931lbd.62.1374612628950;
Tue, 23 Jul 2013 13:50:28 -0700 (PDT)
Received: by 10.112.160.104 with HTTP; Tue, 23 Jul 2013 13:50:28 -0700 (PDT)
In-Reply-To: <CANEZrP2hn3oXp4CU7-85vpSLc_3GGnRgfQNKDc+28jkB2DE2JA@mail.gmail.com>
References: <CANEZrP2GvgZP_1z3EoSs3p+db7tZB6JfEVAewLpGE5eRpGgR3w@mail.gmail.com>
<CAAS2fgT+GPgOtvvrjKozYc-Swqw-+HPcyZY5MbqvY9oEhiWRuA@mail.gmail.com>
<CANEZrP2hn3oXp4CU7-85vpSLc_3GGnRgfQNKDc+28jkB2DE2JA@mail.gmail.com>
Date: Tue, 23 Jul 2013 13:50:28 -0700
Message-ID: <CAAS2fgR7evOkrTpX75EQgJzuDUBqGOKCAvWJR_5T64REOJmJ8A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.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
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.3 URI_HEX URI: URI hostname has long hexadecimal sequence
0.0 NUMERIC_HTTP_ADDR URI: Uses a numeric IP address in URL
-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: 1V1jXX-0000bt-OH
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Linux packaging letter
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, 23 Jul 2013 20:50:39 -0000
On Tue, Jul 23, 2013 at 1:32 PM, Mike Hearn <mike@plan99.net> wrote:
> Yes. Someone decided to actually delete the people who had signed so far =
and
Some people/person went and actually started making substantive edits
to the text.
The text it's rolled back to is missing the last copyedits from last night =
too.
The text that had been ACKed last night was a3e52973, available at
http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-b=
itcoin.md
As far as the PGP goes=E2=80=94
I think using the PGP is good: it's making use of the right tools,
avoids issues like we just had where people go changing the content
after names had been affixed, shows solidarity with people building
security infrastructure that our ecosystem depends on. If you only
use it occasionally then its easy for someone to strip it when it _is_
needed and disguise that just as regular non-use. It's my general
view that for people working in our domain basic competence and use of
these tools, even when they kinda stink, is a kind of civic hygiene.
At the same time it's not urgent. It's poorly used by people and will
be ignored by most but packagers are the most frequent users of it
that I've encountered. Fortunately, it's harmless in any case.
If people are interested in offering PGP signatures of it:
wget http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-=
and-bitcoin.md
gpg --clearsign 20130723-linux-distribution-packaging-and-bitcoin.md
and post the little signature asc. The result composes nicely:
http://luke.dashjr.org/tmp/code/20130723-linux-distribution-packaging-and-b=
itcoin.md.asc
|
