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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <theymos@mm.st>) id 1R1kVK-00075i-SK
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 19:43:18 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of mm.st
designates 66.111.4.28 as permitted sender)
client-ip=66.111.4.28; envelope-from=theymos@mm.st;
helo=out4.smtp.messagingengine.com;
Received: from out4.smtp.messagingengine.com ([66.111.4.28])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1R1kVK-0001WG-0e
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 19:43:18 +0000
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 79B3224C02
for <bitcoin-development@lists.sourceforge.net>;
Thu, 8 Sep 2011 15:43:12 -0400 (EDT)
Received: from web3.messagingengine.com ([10.202.2.213])
by compute3.internal (MEProxy); Thu, 08 Sep 2011 15:43:12 -0400
Received: by web3.messagingengine.com (Postfix, from userid 99)
id 5489E7C0590; Thu, 8 Sep 2011 15:43:12 -0400 (EDT)
Message-Id: <1315510992.9621.140258138898885@webmail.messagingengine.com>
X-Sasl-Enc: oWqFm8/L+3bnEf2h76T/2QeafbEPkMiyKeLW52clWUbt 1315510992
From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
In-Reply-To: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
Date: Thu, 08 Sep 2011 14:43:12 -0500
X-Spam-Score: -1.5 (-)
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
(theymos[at]mm.st)
-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.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1R1kVK-0001WG-0e
Subject: Re: [Bitcoin-development] Alert System
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: Thu, 08 Sep 2011 19:43:18 -0000
The alert system will be very important if there are ever any critical
problems in the network. For example, it is currently Bitcoin's only
defense against an attacker with >50% of the computational power, where
alerts would be used to tell people to stop accepting transactions.
Displaying a message is pretty harmless. In fact, I don't think the
message is prominent enough. The GUI client should not allow people to
see received transactions or send new transactions while an alert is in
effect (with an opt-out), and there should be an opt-in feature that
puts RPC into safe mode in response to an alert.
Alerts are no worse than transactions as a DoS attack vector. They're
much safer than typical HTTPS because there are no CAs that can break
its security.
(FYI: I also have a copy of the alert key.)
|
