public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Egginger <bitcoin@olivere.de>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fake PGP key for Gavin
Date: Sun, 23 Mar 2014 01:59:50 +0100	[thread overview]
Message-ID: <532E3206.3090005@olivere.de> (raw)
In-Reply-To: <CANEZrP0NeDetSLXjtWnCaYYjYcdhsa=ne=a6NJOnvEp8yr7YaA@mail.gmail.com>

Am 22.03.2014 18:03, schrieb Mike Hearn:
> In case you didn't see this yet,
> 
> http://gavintech.blogspot.ch/2014/03/it-aint-me-ive-got-pgp-imposter.html
> 
> If you're using PGP to verify Bitcoin downloads, it's very important
> that you check you are using the right key. Someone seems to be creating
> fake PGP keys that are used to sign popular pieces of crypto software,
> probably to make a MITM attack (e.g. from an intelligence agency) seem
> more legitimate.

From the user's perspective: In the beginning I found it difficult to
find the keys. At last I have made this side for documentation:

https://www.olivere.de/blog/archives/2013/06/02/install_bitcoin_client/

Okay, is outdated meanwhile ...

Normally people fetch the keys by key-id from a well known key server.
Not because they are paranoid, but because it is the most convenient
method under Linux.

A Google search for Gavin+Andresen+gpg brings me herein:

http://sourceforge.net/p/bitcoin/mailman/message/30551147/

Key-Id?

Nevertheless, I'm glad that you guys signed anything. That makes me
sleep better. I really check this.

- oliver

GPG: https://olivere.de/gpg



  parent reply	other threads:[~2014-03-23  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 17:03 [Bitcoin-development] Fake PGP key for Gavin Mike Hearn
2014-03-22 17:33 ` Gavin Andresen
2014-03-22 18:21 ` Peter Todd
2014-03-23  0:59 ` Oliver Egginger [this message]
2014-03-23 22:12 ` Troy Benjegerdes
2014-03-24 19:44   ` The Doctor

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=532E3206.3090005@olivere.de \
    --to=bitcoin@olivere.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.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