From: Harald Schilly <harald@schil.ly>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin2013 Speakers: Include your PGP fingerprint in your slides
Date: Tue, 14 May 2013 21:39:46 +0200 [thread overview]
Message-ID: <CAGG4CB5K32pbJ7qGyjLfB1yvvbTYmU_3eeLh1LWfUnyqkWq6RA@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhKpDQJAqNuh0oddO1GmugfZAznGjk0sOdokqDAPWFibJQ@mail.gmail.com>
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% attack
> 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 … --auto-key-locate pka -r email@address.domain
H
next prev parent reply other threads:[~2013-05-14 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 18:41 [Bitcoin-development] Bitcoin2013 Speakers: Include your PGP fingerprint in your slides Peter Todd
2013-05-14 19:16 ` Melvin Carvalho
2013-05-14 19:31 ` Peter Todd
2013-05-14 19:39 ` Harald Schilly [this message]
2013-05-14 20:12 ` Adam Back
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGG4CB5K32pbJ7qGyjLfB1yvvbTYmU_3eeLh1LWfUnyqkWq6RA@mail.gmail.com \
--to=harald@schil.ly \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox