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
|
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 <marek@palatinus.cz>) id 1RcSI6-0000oz-FY
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Dec 2011 01:45:22 +0000
X-ACL-Warn:
Received: from mail-ey0-f175.google.com ([209.85.215.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RcSI5-00075D-2L
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Dec 2011 01:45:22 +0000
Received: by eaal1 with SMTP id l1so6331791eaa.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 18 Dec 2011 17:45:14 -0800 (PST)
Received: by 10.204.154.136 with SMTP id o8mr4570487bkw.112.1324259114504;
Sun, 18 Dec 2011 17:45:14 -0800 (PST)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.204.168.15 with HTTP; Sun, 18 Dec 2011 17:44:42 -0800 (PST)
In-Reply-To: <20111219011417.GA16815@ulyssis.org>
References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com>
<CAJ1JLtuhwdBC8jJsmS3pTUixdLwh0haB-Gq_CdEmEWYN0-z+QA@mail.gmail.com>
<CAGQP0AH+J5Jo524o+EL9zNdHgpfTorTsyB+Ut4x0W-d9x84JZQ@mail.gmail.com>
<201112181644.44134.luke@dashjr.org>
<CAJna-Hhg9DO4jeuU3nEL2jJGPyxZXpeOLTQe1w8zjT6wqi+kXQ@mail.gmail.com>
<20111219011417.GA16815@ulyssis.org>
From: slush <slush@centrum.cz>
Date: Mon, 19 Dec 2011 02:44:42 +0100
X-Google-Sender-Auth: qrrVqiAIfrhoXAsI9ZIW0r0ASj4
Message-ID: <CAJna-HjyZv2y9grNdnKKG8k6tn7jdW=zL=vtrALpeW8jkuzV6Q@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=00151761ca761c512304b4681a06
X-Spam-Score: 1.3 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 LOTS_OF_MONEY Huge... sums of money
0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RcSI5-00075D-2L
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] [BIP 15] Aliases
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: Mon, 19 Dec 2011 01:45:22 -0000
--00151761ca761c512304b4681a06
Content-Type: text/plain; charset=ISO-8859-1
Pieter, it was more rhetorical question than asking for explanation, but
thanks anyway. As an Internet application developer, I of course understand
security issues while using HTTPS and CA.
I have a gut feeling that there simply does not exist any single solution
which is both easy to use and secure enough. At least nobody mentioned it
yet. And if I need to choose between easy solution or secure solution for
aliases, I'll pick that easy one. I mean - we need some solution which will
be easy enough for daily use; it is something what we currently don't have.
But if I want to be really really sure I'm using correct destination for
paying $1mil for a house, I can every time ask for real bitcoin addresses,
this is that secure way which we currently have.
slush
On Mon, Dec 19, 2011 at 2:14 AM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
> On Mon, Dec 19, 2011 at 12:58:37AM +0100, slush wrote:
> > Maybe I'm retarded, but where's the point in providing alliases
> containing
> > yet another hash in URL?
>
> Any DNS-based alias system is vulnerable to spoofing. If I can make
> people's
> DNS server believe that mining.cz points to my IP, I'll receive payments
> to
> you...
>
> If no trusted CA is used to authenticate the communication, there is no way
> to be sure the one you are asking how to pay, is the person you want to
> pay.
> Therefore, one solution is to put a bitcoin address in the identification
> string itself, and requiring SSL communication authenticated using the
> respective key.
>
> This makes the identification strings obviously less useful as aliases,
> but pure aliases in the sense of human-typable strings have imho
> limited usefulness anyway - in most cases these identification strings
> will be communicated through other electronic means anyway.
>
> Furthermore, the embedded bitcoin address could be hidden from the user:
> retrieved when first connecting, and stored together with the URI in
> an address book. Like ssh, it could warn the user if the key changes
> (which wil be ignored by most users anyway, but what do you do about
> that?)
>
> --
> Pieter
>
>
> ------------------------------------------------------------------------------
> Learn Windows Azure Live! Tuesday, Dec 13, 2011
> Microsoft is holding a special Learn Windows Azure training event for
> developers. It will provide a great way to learn Windows Azure and what it
> provides. You can attend the event by watching it streamed LIVE online.
> Learn more at http://p.sf.net/sfu/ms-windowsazure
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--00151761ca761c512304b4681a06
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Pieter, it was more rhetorical question than asking for explanation, but th=
anks anyway. As an Internet application developer, I of course understand s=
ecurity issues while using HTTPS and CA.<div><br></div><div>I have a gut fe=
eling that there simply does not exist any single solution which is both ea=
sy to use and secure enough. At least nobody mentioned it yet. And if I nee=
d to choose between easy solution or secure solution for aliases, I'll =
pick that easy one. I mean - we need some solution which will be easy enoug=
h for daily use; it is something what we currently don't have. But if I=
want to be really really sure I'm using correct destination for paying=
$1mil for a house, I can every time ask for real bitcoin addresses, this i=
s that secure way which we currently have.=A0</div>
<div><br></div><div>slush<br><br><div class=3D"gmail_quote">On Mon, Dec 19,=
2011 at 2:14 AM, Pieter Wuille <span dir=3D"ltr"><<a href=3D"mailto:pie=
ter.wuille@gmail.com">pieter.wuille@gmail.com</a>></span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<div class=3D"im">On Mon, Dec 19, 2011 at 12:58:37AM +0100, slush wrote:<br=
>
> Maybe I'm retarded, but where's the point in providing alliase=
s containing<br>
> yet another hash in URL?<br>
<br>
</div>Any DNS-based alias system is vulnerable to spoofing. If I can make p=
eople's<br>
DNS server believe that <a href=3D"http://mining.cz" target=3D"_blank">mini=
ng.cz</a> points to my IP, I'll receive payments to<br>
you...<br>
<br>
If no trusted CA is used to authenticate the communication, there is no way=
<br>
to be sure the one you are asking how to pay, is the person you want to pay=
.<br>
Therefore, one solution is to put a bitcoin address in the identification<b=
r>
string itself, and requiring SSL communication authenticated using the<br>
respective key.<br>
<br>
This makes the identification strings obviously less useful as aliases,<br>
but pure aliases in the sense of human-typable strings have imho<br>
limited usefulness anyway - in most cases these identification strings<br>
will be communicated through other electronic means anyway.<br>
<br>
Furthermore, the embedded bitcoin address could be hidden from the user:<br=
>
retrieved when first connecting, and stored together with the URI in<br>
an address book. Like ssh, it could warn the user if the key changes<br>
(which wil be ignored by most users anyway, but what do you do about<br>
that?)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Pieter<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Learn Windows Azure Live! =A0Tuesday, Dec 13, 2011<br>
Microsoft is holding a special Learn Windows Azure training event for<br>
developers. It will provide a great way to learn Windows Azure and what it<=
br>
provides. You can attend the event by watching it streamed LIVE online.<br>
Learn more at <a href=3D"http://p.sf.net/sfu/ms-windowsazure" target=3D"_bl=
ank">http://p.sf.net/sfu/ms-windowsazure</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></div>
--00151761ca761c512304b4681a06--
|
