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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <harald.schilly@gmail.com>) id 1UcL5S-0006V9-30
for bitcoin-development@lists.sourceforge.net;
Tue, 14 May 2013 19:40:38 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.176 as permitted sender)
client-ip=209.85.223.176; envelope-from=harald.schilly@gmail.com;
helo=mail-ie0-f176.google.com;
Received: from mail-ie0-f176.google.com ([209.85.223.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UcL5C-0007LU-Dz
for bitcoin-development@lists.sourceforge.net;
Tue, 14 May 2013 19:40:38 +0000
Received: by mail-ie0-f176.google.com with SMTP id at1so1878733iec.7
for <bitcoin-development@lists.sourceforge.net>;
Tue, 14 May 2013 12:40:17 -0700 (PDT)
X-Received: by 10.50.72.52 with SMTP id a20mr3156642igv.36.1368560417049; Tue,
14 May 2013 12:40:17 -0700 (PDT)
MIME-Version: 1.0
Sender: harald.schilly@gmail.com
Received: by 10.64.7.164 with HTTP; Tue, 14 May 2013 12:39:46 -0700 (PDT)
In-Reply-To: <CAKaEYhKpDQJAqNuh0oddO1GmugfZAznGjk0sOdokqDAPWFibJQ@mail.gmail.com>
References: <20130514184120.GB18341@petertodd.org>
<CAKaEYhKpDQJAqNuh0oddO1GmugfZAznGjk0sOdokqDAPWFibJQ@mail.gmail.com>
From: Harald Schilly <harald@schil.ly>
Date: Tue, 14 May 2013 21:39:46 +0200
X-Google-Sender-Auth: tRSgM2K5WmDumEs8eOQnHRg9nI0
Message-ID: <CAGG4CB5K32pbJ7qGyjLfB1yvvbTYmU_3eeLh1LWfUnyqkWq6RA@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.3 (/)
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
(harald.schilly[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline
X-Headers-End: 1UcL5C-0007LU-Dz
Subject: Re: [Bitcoin-development] Bitcoin2013 Speakers: Include your PGP
fingerprint in your slides
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, 14 May 2013 19:40:38 -0000
On Tue, May 14, 2013 at 9:16 PM, Melvin Carvalho
<melvincarvalho@gmail.com> wrote:
> Just out of curiosity, could PGP keyservers suffer from a similar 51% att=
ack
> as the bitcoin network?
Well, no, and yes. It doesn't work like that.
If you have your own domain, you can store your key there as a TXT entry.
$ dig +short harald._pka.schil.ly. TXT
and even use it automatically:
$ gpg =85 --auto-key-locate pka -r email@address.domain
H
|
