Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.175 as permitted sender)
	client-ip=209.85.213.175; envelope-from=witchspace81@gmail.com;
	helo=mail-yx0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <20110908162014.GA7513@ulyssis.org>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
	<4E68D968.1080604@gmail.com>
	<CAK5y1FhyCCwL+w4Uo6Xht9BFkZiAmNCeywACnx=eQa6f2iFP2Q@mail.gmail.com>
	<20110908162014.GA7513@ulyssis.org>
Date: Thu, 8 Sep 2011 16:37:01 +0000
Message-ID: <CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd6aeb08d876304ac70abc2
Cc: bitcoin-development@lists.sourceforge.net, David Perry <enmaku@gmail.com>
Subject: Re: [Bitcoin-development] Alert System
Precedence: list

--000e0cd6aeb08d876304ac70abc2
Content-Type: text/plain; charset=ISO-8859-1

There is a lot of complaining about this alert system, but I really don't
see the problem.

As others have already said, it's just a message. Even if someone managed to
compromise the private key, the most they could do is spam graffiti messages
or try phishing. There are much worse things that could happen to the
network (in which case an alert system could come in very handy). It's just
not worth worrying about.

JS

On Thu, Sep 8, 2011 at 4:20 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:

> On Thu, Sep 08, 2011 at 09:09:12AM -0700, David Perry wrote:
> > @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?
>
> Yes, Satoshi transferred the key to Gavin when he "left". I agree we should
> keep it, btw. There have been suggestions before on this list to use the
> alert system to ask people to upgrade to recent versions of the client (eg.
> the disconnect issue 0.3.20-0.3.23 had). I feel there may come a moment
> when
> we really need to use it for that purpose.
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops?   How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

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

There is a lot of complaining about this alert system, but I really don&#39=
;t see the problem. <br><br>As others have already said, it&#39;s just a me=
ssage. Even if someone managed to compromise the private key, the most they=
 could do is spam graffiti messages or try phishing. There are much worse t=
hings that could happen to the network (in which case an alert system could=
 come in very handy). It&#39;s just not worth worrying about.<br>
<br>JS<br><br><div class=3D"gmail_quote">On Thu, Sep 8, 2011 at 4:20 PM, Pi=
eter Wuille <span dir=3D"ltr">&lt;<a href=3D"mailto:pieter.wuille@gmail.com=
">pieter.wuille@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;">
<div><div></div><div class=3D"h5">On Thu, Sep 08, 2011 at 09:09:12AM -0700,=
 David Perry wrote:<br>
&gt; @Steve re &quot;Who knows, it might be the only way we&#39;ll ever hea=
r from Satoshi<br>
&gt; again.&quot;<br>
&gt;<br>
&gt; That brings up a good point... Does anyone aside from Satoshi actually=
 have<br>
&gt; the ability to send such an alert? Should we at the very least change =
the<br>
&gt; alert system to give such privileges to current devs and ensure that t=
hat if<br>
&gt; the missing Mr. Satoshi has had his key compromised we don&#39;t see a=
n<br>
&gt; authoritative-looking alert come up from a malicious source?<br>
<br>
</div></div>Yes, Satoshi transferred the key to Gavin when he &quot;left&qu=
ot;. I agree we should<br>
keep it, btw. There have been suggestions before on this list to use the<br=
>
alert system to ask people to upgrade to recent versions of the client (eg.=
<br>
the disconnect issue 0.3.20-0.3.23 had). I feel there may come a moment whe=
n<br>
we really need to use it for that purpose.<br>
<br>
--<br>
<font color=3D"#888888">Pieter<br>
</font><div><div></div><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Doing More with Less: The Next Generation Virtual Desktop<br>
What are the key obstacles that have prevented many mid-market businesses<b=
r>
from deploying virtual desktops? =A0 How do next-generation virtual desktop=
s<br>
provide companies an easier-to-deploy, easier-to-manage and more affordable=
<br>
virtual desktop model.<a href=3D"http://www.accelacomm.com/jaw/sfnl/114/514=
26474/" target=3D"_blank">http://www.accelacomm.com/jaw/sfnl/114/51426474/<=
/a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br>

--000e0cd6aeb08d876304ac70abc2--