blob: 298d237b318ac05c9c0c8945cf63208784aeb401 (
plain)
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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <vv01f@riseup.net>) id 1WUZLd-00023M-Mk
for bitcoin-development@lists.sourceforge.net;
Mon, 31 Mar 2014 10:21:45 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of riseup.net
designates 198.252.153.129 as permitted sender)
client-ip=198.252.153.129; envelope-from=vv01f@riseup.net;
helo=mx1.riseup.net;
Received: from mx1.riseup.net ([198.252.153.129])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WUZLb-00038G-PK
for bitcoin-development@lists.sourceforge.net;
Mon, 31 Mar 2014 10:21:45 +0000
Received: from fruiteater.riseup.net (fruiteater-pn.riseup.net [10.0.1.74])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.riseup.net",
Issuer "Gandi Standard SSL CA" (not verified))
by mx1.riseup.net (Postfix) with ESMTPS id B435A4EDFA
for <bitcoin-development@lists.sourceforge.net>;
Mon, 31 Mar 2014 03:21:37 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
(Authenticated sender: vv01f@fruiteater.riseup.net)
with ESMTPSA id 5DEC3F1E
Message-ID: <5339418F.1050800@riseup.net>
Date: Mon, 31 Mar 2014 12:21:03 +0200
From: vv01f <vv01f@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
X-Enigmail-Version: 1.5.1
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="----enig2DVNFKTHHVNAMMRQWWTFI"
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
X-Spam-Score: -2.1 (--)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [198.252.153.129 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
-0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
X-Headers-End: 1WUZLb-00038G-PK
Subject: [Bitcoin-development] secure assigned bitcoin address directory
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, 31 Mar 2014 10:21:45 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2DVNFKTHHVNAMMRQWWTFI
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Some users on bitcointalk[0] would like to have their vanity addresses
available for others easily to find and verify the ownership over a kind
of WoT. Right now they sign their own addresses and quote them in the
forums.
As I pointed out there already the centralized storage in the forums is
not secury anyhow and signed messages could be swapped easily with the
next hack of the forums.
Is that use case taken care of in any plans already?
I thought about abusing pgp keyservers but that would suit for single
vanity addresses only.
It seems webfinger could be part of a solution where servers of a
business can tell and proof you if a specific address is owned by them.
[0] https://bitcointalk.org/index.php?topic=3D502538
[1] https://bitcointalk.org/index.php?topic=3D505095
------enig2DVNFKTHHVNAMMRQWWTFI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBAgAGBQJTOUGPAAoJECTLpwatJtn75IcP/iRMesNTyvW2lyzxGuKC4eYS
mfNLr84uGIhBSUcLWqMWO+r/4Lv0BvSJhrzXIUGo4XTCtGyYDGdWYroNvJf7HBhR
TwC8FhCTsfT2fchalhPgLE3Q6ulJDdvEgLwzfsU9Tkas88KAk8Dkavk2vIjtQBS5
pAe2IH0pLPcwKrpqlWMUFCTEJi2nxzo16hEOucuwkFsF5LhxOl3inZ9yvDsXdZEM
ZggbuZVQ5eY7HeVVRVLQxpUaw8N6OFHqueJ8x6Wl3vWCx4oF+ChKgoFU20yzwdlN
9niiiMkqsxgNumpTod7b0wFvsH6NI7W9eSXMlqGtuqjwdqUiKtkbk2QxWPIY9gZD
XHSsbqDSLFtf7fouPmaQXUwjkPrNKxNBzAnEOk2d32DauIyPOOrbK/xEVtQnytMv
YcVDIxevJPuQIQXQwBvlycQp3SseKhKcsDoZt24xQQ2ckKEM0w+UbiBX64Rdoqe7
i8i3N0LNzRBkXJ4luLlnQ9hQPWNwG/kIBPEWvMHshhbHLLuVDm9AP8RAxmeqPDl+
GkmSYNqS01zaQNnRN4fWe6NCKbg89yssnprPR8AT+hgK70RUsuq2m+1V4cz+0biO
GPeB1mt703CW120VhpSP0DNamofUTCJXa235wwAwNY7znrNJaJ5miSoFQhylk55a
GUROBCULItr4jraElFlk
=qROB
-----END PGP SIGNATURE-----
------enig2DVNFKTHHVNAMMRQWWTFI--
|
