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 <enmaku@gmail.com>) id 1R1hAJ-00051r-1m
	for bitcoin-development@lists.sourceforge.net;
	Thu, 08 Sep 2011 16:09:23 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.47 as permitted sender)
	client-ip=209.85.213.47; envelope-from=enmaku@gmail.com;
	helo=mail-yw0-f47.google.com; 
Received: from mail-yw0-f47.google.com ([209.85.213.47])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
	(Exim 4.76) id 1R1hAD-00077s-MU
	for bitcoin-development@lists.sourceforge.net;
	Thu, 08 Sep 2011 16:09:23 +0000
Received: by ywa12 with SMTP id 12so959437ywa.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 08 Sep 2011 09:09:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.158.136 with SMTP id h8mr364433icx.51.1315498152065; Thu,
	08 Sep 2011 09:09:12 -0700 (PDT)
Received: by 10.231.16.13 with HTTP; Thu, 8 Sep 2011 09:09:12 -0700 (PDT)
In-Reply-To: <4E68D968.1080604@gmail.com>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
	<4E68D968.1080604@gmail.com>
Date: Thu, 8 Sep 2011 09:09:12 -0700
Message-ID: <CAK5y1FhyCCwL+w4Uo6Xht9BFkZiAmNCeywACnx=eQa6f2iFP2Q@mail.gmail.com>
From: David Perry <enmaku@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=90e6ba6e8adc0e7bf804ac704862
X-Spam-Score: -0.6 (/)
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
	(enmaku[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1R1hAD-00077s-MU
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 16:09:23 -0000

--90e6ba6e8adc0e7bf804ac704862
Content-Type: text/plain; charset=ISO-8859-1

@Steve re "Who knows, it might be the only way we'll ever hear from Satoshi
again."

That brings up a good point... Does anyone aside from Satoshi actually have
the ability to send such an alert? Should we at the very least change the
alert system to give such privileges to current devs and ensure that that if
the missing Mr. Satoshi has had his key compromised we don't see an
authoritative-looking alert come up from a malicious source?

--90e6ba6e8adc0e7bf804ac704862
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

@Steve re &quot;<span class=3D"Apple-style-span" style=3D"color: rgb(85, 85=
, 85); font-family: monospace; font-size: 11px; line-height: 16px; white-sp=
ace: pre; background-color: rgb(255, 255, 255); ">Who knows, it might be th=
e only way we&#39;ll ever hear from Satoshi again.</span>&quot;<div>
<br></div><div>That brings up a good point... Does anyone aside from Satosh=
i actually have the ability to send such an alert? Should we at the very le=
ast change the alert system to give such=A0privileges=A0to current devs and=
 ensure that that if the missing Mr. Satoshi has had his key compromised we=
 don&#39;t see an authoritative-looking alert come up from a malicious sour=
ce?</div>

--90e6ba6e8adc0e7bf804ac704862--