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
|
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 <will@phase.net>) id 1RaGGU-0001zX-VG
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 00:30:38 +0000
X-ACL-Warn:
Received: from mail-gx0-f175.google.com ([209.85.161.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1RaGGT-0004BO-OW
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Dec 2011 00:30:38 +0000
Received: by ggnh1 with SMTP id h1so7722600ggn.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 12 Dec 2011 16:30:32 -0800 (PST)
Received: by 10.182.88.99 with SMTP id bf3mr3489560obb.73.1323733098209; Mon,
12 Dec 2011 15:38:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.16.74 with HTTP; Mon, 12 Dec 2011 15:37:58 -0800 (PST)
In-Reply-To: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
From: Will <will@phase.net>
Date: Mon, 12 Dec 2011 23:37:58 +0000
Message-ID: <CAHQs=o7ieTM3axeDvmODY+o6pMXDzy2V70-bKV31wKWXKBN+FQ@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=14dae9399d3b18a13004b3eda11a
X-Spam-Score: 0.2 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
-0.8 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RaGGT-0004BO-OW
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: Tue, 13 Dec 2011 00:30:39 -0000
--14dae9399d3b18a13004b3eda11a
Content-Type: text/plain; charset=ISO-8859-1
Are there any PGP key servers that support EC key pairs? OpenPGP Spec
RFC2440 defines key types for EC, just not sure if they were ever
implemented on the keyserver side. Could even have a similar 'web of
trust' using private keys to sign people's identities similar to PGP.
Will
On 12 December 2011 23:16, Zell Faze <zellfaze@yahoo.com> wrote:
> I agree with Luke-Jr. We need to try to find a decentralized solution if
> we are going to implement BIP 15. Bitcoin needs to remain decentralized in
> every aspect of the protocol or we lose its greatest strength.
>
> I feel like the HTTPS idea would be a great idea for a client feature, but
> not really something that should be added to the protocol.
>
> --- On Mon, 12/12/11, Luke-Jr <luke@dashjr.org> wrote:
>
> > From: Luke-Jr <luke@dashjr.org>
> > Subject: Re: [Bitcoin-development] [BIP 15] Aliases
> > To: bitcoin-development@lists.sourceforge.net, "Amir Taaki" <
> zgenjix@yahoo.com>
> > Date: Monday, December 12, 2011, 5:32 PM
> > FirstBits looks nice at glance, but
> > is bound to create a gold-rush to grab
> > every nice-looking FirstBits address.
> >
> > HTTPS is only as secure as the (centralized) CAs, thus not
> > really any better
> > than TXT records.
> >
> > I don't think an address of some form is avoidable.
>
>
>
> ------------------------------------------------------------------------------
> 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
>
--14dae9399d3b18a13004b3eda11a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Are there any PGP key servers that support EC key pairs?=A0 OpenPGP Spec RF=
C2440 defines key types for EC, just not sure if they were ever implemented=
on the keyserver side.=A0 Could even have a similar 'web of trust'=
using private keys to sign people's identities similar to PGP.<br>
<br>Will<br><br><div class=3D"gmail_quote">On 12 December 2011 23:16, Zell =
Faze <span dir=3D"ltr"><<a href=3D"mailto:zellfaze@yahoo.com">zellfaze@y=
ahoo.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree with Luke-Jr. =A0We need to try to find a decentralized solution if=
we are going to implement BIP 15. =A0Bitcoin needs to remain decentralized=
in every aspect of the protocol or we lose its greatest strength.<br>
<br>
I feel like the HTTPS idea would be a great idea for a client feature, but =
not really something that should be added to the protocol.<br>
<br>
--- On Mon, 12/12/11, Luke-Jr <<a href=3D"mailto:luke@dashjr.org">luke@d=
ashjr.org</a>> wrote:<br>
<br>
> From: Luke-Jr <<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</=
a>><br>
> Subject: Re: [Bitcoin-development] [BIP 15] Aliases<br>
> To: <a href=3D"mailto:bitcoin-development@lists.sourceforge.net">bitco=
in-development@lists.sourceforge.net</a>, "Amir Taaki" <<a hre=
f=3D"mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>><br>
> Date: Monday, December 12, 2011, 5:32 PM<br>
<div class=3D"HOEnZb"><div class=3D"h5">> FirstBits looks nice at glance=
, but<br>
> is bound to create a gold-rush to grab<br>
> every nice-looking FirstBits address.<br>
><br>
> HTTPS is only as secure as the (centralized) CAs, thus not<br>
> really any better<br>
> than TXT records.<br>
><br>
> I don't think an address of some form is avoidable.<br>
<br>
<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>
--14dae9399d3b18a13004b3eda11a--
|
