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
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <decker.christian@gmail.com>) id 1R1xCE-0000hF-Ku
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Sep 2011 09:16:26 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175;
envelope-from=decker.christian@gmail.com;
helo=mail-wy0-f175.google.com;
Received: from mail-wy0-f175.google.com ([74.125.82.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R1xCC-0005KI-9A
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Sep 2011 09:16:26 +0000
Received: by wyf19 with SMTP id 19so1800930wyf.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Sep 2011 02:16:18 -0700 (PDT)
Received: by 10.227.121.68 with SMTP id g4mr56585wbr.95.1315559778079; Fri, 09
Sep 2011 02:16:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.55.133 with HTTP; Fri, 9 Sep 2011 02:15:38 -0700 (PDT)
In-Reply-To: <3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com>
References: <CAK5y1FhQLWXtqHfB3HymOkZ-5LdTqdEkX8bM=nOGhFeZrOPwgA@mail.gmail.com>
<CAJNQ0suvvAC+TBu5Cbt+Q2=aycMnVHRXXGccEdytSZOj10w5JA@mail.gmail.com>
<CANEZrP2sbLc-ATpf7Uu1S6UQfhd2LPPoHRJmvjZuzH2CUS-TqQ@mail.gmail.com>
<201109081315.12643.luke@dashjr.org>
<CAHQs=o5xSLa7+eMRT+eskdMw=jVNwxj9gGYyjqtwZyxXbnRxcg@mail.gmail.com>
<3658b238-b1bf-4fde-8880-d50c3eaa8ed9@email.android.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Fri, 9 Sep 2011 11:15:38 +0200
Message-ID: <CALxbBHVnwdq7YAGo9pEbQOqy3A=u9ieufozr2T1Y_cuoQa8U6A@mail.gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=00248c0ef25e40d4bd04ac7ea1b6
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
(decker.christian[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
X-Headers-End: 1R1xCC-0005KI-9A
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: Fri, 09 Sep 2011 09:16:26 -0000
--00248c0ef25e40d4bd04ac7ea1b6
Content-Type: text/plain; charset=ISO-8859-1
Resending to mailing list as I replied directly...
On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker <
decker.christian@gmail.com> wrote:
>
>
> Will <will@phase.net> wrote:
>
> >> In fact, I think the alert system should relay (note, NOT display)
> >messages
> >> *regardless of the key used*, so it isn't yet another "our client
> >gets
> >> special
> >> status" thing, and can be used for other clients as well.
> >>
> >>
> >> Be careful though, if you relay everything, it suddenly *does* have
> >DDoS
> >potential...
> >
> >no more than other messages such as transactions.
> Only verified and valid trandactions are forwarded which is desired as it
> costs the sender a fee if he attempts to spam, messages have no such
> penalty.
> >
> >>Maybe require a proof-of-work then?
> >
> >kind of defeats the purpose of the alert if it takes a long time to
> >issue
> >one.
> >
> >I think leave the alert in, but relay alert messages even if they don't
> >use
> >the correct key. This means that if we later decide to add new keys to
> >the
> >alert root trust then older clients will still relay these.
> >
> >my .02btc
> >
> >Will
> I'm for keeping it in there as well, maybe even extend it with a mechanism
> to sign other certificates giving alternative client developers the ability
> to issue their own alerts. Think ssl certificates...
>
> Regards,
> Chris
>
> >------------------------------------------------------------------------------
> >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
>
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
--00248c0ef25e40d4bd04ac7ea1b6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">Resending to mailing list as I replied directly.=
..<br>On Thu, Sep 8, 2011 at 11:03 PM, Christian Decker <span dir=3D"ltr">&=
lt;<a href=3D"mailto:decker.christian@gmail.com">decker.christian@gmail.com=
</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im"><br>
<br>
Will <<a href=3D"mailto:will@phase.net">will@phase.net</a>> wrote:<br=
>
<br>
>> In fact, I think the alert system should relay (note, NOT display)=
<br>
>messages<br>
>> *regardless of the key used*, so it isn't yet another "ou=
r client<br>
>gets<br>
>> special<br>
>> status" thing, and can be used for other clients as well.<br>
>><br>
>><br>
>> Be careful though, if you relay everything, it suddenly *does* hav=
e<br>
>DDoS<br>
>potential...<br>
><br>
>no more than other messages such as transactions.<br>
</div>Only verified and valid trandactions are forwarded which is desired a=
s it costs the sender a fee if he attempts to spam, messages have no such p=
enalty.<br>
<div class=3D"im">><br>
>>Maybe require a proof-of-work then?<br>
><br>
>kind of defeats the purpose of the alert if it takes a long time to<br>
>issue<br>
>one.<br>
><br>
>I think leave the alert in, but relay alert messages even if they don&#=
39;t<br>
>use<br>
>the correct key. =A0This means that if we later decide to add new keys =
to<br>
>the<br>
>alert root trust then older clients will still relay these.<br>
><br>
>my .02btc<br>
><br>
>Will<br>
</div>I'm for keeping it in there as well, maybe even extend it with a =
mechanism to sign other certificates giving alternative client developers t=
he ability to issue their own alerts. Think ssl certificates...<br>
<br>
Regards,<br>
Chris<br>
<div><div></div><div class=3D"h5">>-------------------------------------=
-----------------------------------------<br>
>Doing More with Less: The Next Generation Virtual Desktop<br>
>What are the key obstacles that have prevented many mid-market<br>
>businesses<br>
>from deploying virtual desktops? =A0 How do next-generation virtual<br>
>desktops<br>
>provide companies an easier-to-deploy, easier-to-manage and more<br>
>affordable<br>
>virtual desktop<br>
>model.<a href=3D"http://www.accelacomm.com/jaw/sfnl/114/51426474/______=
_________________________________________" target=3D"_blank">http://www.acc=
elacomm.com/jaw/sfnl/114/51426474/_________________________________________=
______</a><br>
>Bitcoin-development mailing list<br>
><a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-de=
velopment@lists.sourceforge.net</a><br>
><a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develop=
ment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoi=
n-development</a><br>
<br>
</div></div><font color=3D"#888888">--<br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br>
</font></blockquote></div><br>
--00248c0ef25e40d4bd04ac7ea1b6--
|
