From: The Doctor <drwho@virtadpt•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Fake PGP key for Gavin
Date: Mon, 24 Mar 2014 12:44:24 -0700 [thread overview]
Message-ID: <53308B18.4070602@virtadpt.net> (raw)
In-Reply-To: <20140323221221.GK3180@nl.grid.coop>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 03/23/2014 03:12 PM, Troy Benjegerdes wrote:
> I find it more likely that fake PGP keys are from corporate
> industrial espionage and/or organized crime outfits. Intelligence
> agencies will stick to compromised X509, network cards, and binary
> code blobs.
We're seeing the same thing happen to a couple of developers active in
the censorship circumvention problem space as well (though it's not
for the first time it's happened).
> Besides, why would an intelligence agency want your bitcoin when
> they can just intercept ASIC miners and make their own?
Perhaps they have other motives for attempting a cybil attack against
developers than trying to acquire Bitcoins. Say, by making it easier
to subtitute alternate versions which are instrumented to make the
users easier to spy upon and later take down?
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
"The enemies know the system. The allies do not." --Jay Jacobs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEAREKAAYFAlMwixgACgkQO9j/K4B7F8FQEACfQG8+5rYDuJd+6P50Bgc8RRfU
Q28AoNdyUbR2k05wTka30OcUUQNK5FcN
=IeMU
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-03-24 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 17:03 Mike Hearn
2014-03-22 17:33 ` Gavin Andresen
2014-03-22 18:21 ` Peter Todd
2014-03-23 0:59 ` Oliver Egginger
2014-03-23 22:12 ` Troy Benjegerdes
2014-03-24 19:44 ` The Doctor [this message]
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=53308B18.4070602@virtadpt.net \
--to=drwho@virtadpt$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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