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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1RcQdR-0001NR-JC
for bitcoin-development@lists.sourceforge.net;
Sun, 18 Dec 2011 23:59:17 +0000
X-ACL-Warn:
Received: from mail-ey0-f175.google.com ([209.85.215.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RcQdQ-0007rK-9n
for bitcoin-development@lists.sourceforge.net;
Sun, 18 Dec 2011 23:59:17 +0000
Received: by eaal1 with SMTP id l1so6280175eaa.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 18 Dec 2011 15:59:10 -0800 (PST)
Received: by 10.204.154.136 with SMTP id o8mr4522272bkw.112.1324252748302;
Sun, 18 Dec 2011 15:59:08 -0800 (PST)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.204.168.15 with HTTP; Sun, 18 Dec 2011 15:58:37 -0800 (PST)
In-Reply-To: <201112181644.44134.luke@dashjr.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>
From: slush <slush@centrum.cz>
Date: Mon, 19 Dec 2011 00:58:37 +0100
X-Google-Sender-Auth: nJOKx-5eTtE0s35-_hkBXp-nRB4
Message-ID: <CAJna-Hhg9DO4jeuU3nEL2jJGPyxZXpeOLTQe1w8zjT6wqi+kXQ@mail.gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=00151761ca76a7c99204b4669e1d
X-Spam-Score: 1.4 (+)
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.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RcQdQ-0007rK-9n
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: Sun, 18 Dec 2011 23:59:17 -0000
--00151761ca76a7c99204b4669e1d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Maybe I'm retarded, but where's the point in providing alliases containing
yet another hash in URL?
slush
On Sun, Dec 18, 2011 at 10:44 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Sunday, December 18, 2011 4:05:11 PM Jorge Tim=F3n wrote:
> > If we chose the simple URI proposal namecoin can still be integrated
> > to map the IP of the server by those who want to.
> > Does it removes the necessity of the certificates?
> > If so, we should let people decide between HTTP, HTTPS, namecoin or
> > whatever they trust.
>
> How are you going to authenticate the host? Certificates from CAs are how
> HTTPS does it. HTTP is vulnerable. If the URI contains an address (eg,
> bitcoin://remotehost/base58key), the remote host could sign its
> (self-signed)
> SSL key with the ECDSA key to prove authenticity. DNSSEC/namecoin
> presumably
> has some way to do this as well.
>
> > Shouldn't we be also discussing the valid format of the answered
> > message? I mean fields like "amount", "concept" and such.
>
> At some point, a proper protocol to negotiate payment is needed for
> anything
> like this.
>
>
> -------------------------------------------------------------------------=
-----
> 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 i=
t
> 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
>
--00151761ca76a7c99204b4669e1d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Maybe I'm retarded, but where's the point in providing alliases con=
taining yet another hash in URL?<div><br></div><div>slush<br><br><div class=
=3D"gmail_quote">On Sun, Dec 18, 2011 at 10:44 PM, Luke-Jr <span dir=3D"ltr=
"><<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>></span> wro=
te:<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">On Sunday, December 18, 20=
11 4:05:11 PM Jorge Tim=F3n wrote:<br>
> If we chose the simple URI proposal namecoin can still be integrated<b=
r>
> to map the IP of the server by those who want to.<br>
> Does it removes the necessity of the certificates?<br>
> If so, we should let people decide between HTTP, HTTPS, namecoin or<br=
>
> whatever they trust.<br>
<br>
</div>How are you going to authenticate the host? Certificates from CAs are=
how<br>
HTTPS does it. HTTP is vulnerable. If the URI contains an address (eg,<br>
bitcoin://remotehost/base58key), the remote host could sign its (self-signe=
d)<br>
SSL key with the ECDSA key to prove authenticity. DNSSEC/namecoin presumabl=
y<br>
has some way to do this as well.<br>
<div class=3D"im"><br>
> Shouldn't we be also discussing the valid format of the answered<b=
r>
> message? I mean fields like "amount", "concept" an=
d such.<br>
<br>
</div>At some point, a proper protocol to negotiate payment is needed for a=
nything<br>
like this.<br>
<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>
--00151761ca76a7c99204b4669e1d--
|
