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
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1R1hb4-0004SG-EP
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 16:37:02 +0000
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;
Received: from mail-yx0-f175.google.com ([209.85.213.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1R1hb3-00085h-IU
for bitcoin-development@lists.sourceforge.net;
Thu, 08 Sep 2011 16:37:02 +0000
Received: by mail-yx0-f175.google.com with SMTP id 17so995639yxj.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 08 Sep 2011 09:37:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.187.8 with SMTP id k8mr1035858ybf.64.1315499821336; Thu,
08 Sep 2011 09:37:01 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Thu, 8 Sep 2011 09:37:01 -0700 (PDT)
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
X-Spam-Score: -0.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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
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 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R1hb3-00085h-IU
Cc: bitcoin-development@lists.sourceforge.net, David Perry <enmaku@gmail.com>
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:37:02 -0000
--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'=
;t see the problem. <br><br>As others have already said, it'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'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"><<a href=3D"mailto:pieter.wuille@gmail.com=
">pieter.wuille@gmail.com</a>></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>
> @Steve re "Who knows, it might be the only way we'll ever hea=
r from Satoshi<br>
> again."<br>
><br>
> That brings up a good point... Does anyone aside from Satoshi actually=
have<br>
> the ability to send such an alert? Should we at the very least change =
the<br>
> alert system to give such privileges to current devs and ensure that t=
hat if<br>
> the missing Mr. Satoshi has had his key compromised we don't see a=
n<br>
> authoritative-looking alert come up from a malicious source?<br>
<br>
</div></div>Yes, Satoshi transferred the key to Gavin when he "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--
|
