From: Jeff Garzik <jgarzik@bitpay.com>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Justus Ranvier <justusranvier@riseup.net>
Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages
Date: Tue, 19 Aug 2014 20:21:35 -0400 [thread overview]
Message-ID: <CAJHLa0PnvpAaTgaUej=1G7CJ9=BYSjEWvXybfEaG9pFJxsM8fQ@mail.gmail.com> (raw)
In-Reply-To: <3476b0a1-e08a-46bf-9ee4-ef56fcb02d72@email.android.com>
On Tue, Aug 19, 2014 at 8:16 PM, Peter Todd <pete@petertodd.org> wrote:
> On 19 August 2014 19:40:39 GMT-04:00, Jeff Garzik <jgarzik@bitpay.com> wrote:
>>Encryption is of little value if you may deduce the same information
>>by observing packet sizes and timings.
>
> That is simply incorrect. The resources required to do that kind of monitoring are very high; even the NSA can't pull it off consistently for
Hardly. For example, when a new block arrives on the network, a
single observer at a single location may obtain a binary "likely|not
bitcoin protocol" decision from a spike in usage correlated with
sudden, global network activity after a period of inactivity. I'll
not detail all such metrics.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-08-20 0:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+8=xuJ+YDTNjyDW7DvP8KPN_nrFWpE68HvLw6EokFa-B-QGKw@mail.gmail.com>
2014-08-19 9:49 ` [Bitcoin-development] Proposal: Encrypt bitcoin messages Raúl Martínez
[not found] ` <0C0EF7F9-DBBA-4872-897D-63CFA3853726@ricmoo.com>
2014-08-19 15:11 ` Raúl Martínez
2014-08-19 15:30 ` Richard Moore
2014-08-19 16:07 ` Justus Ranvier
2014-08-19 16:38 ` Gregory Maxwell
2014-08-19 16:58 ` Angel Leon
2014-08-19 17:19 ` Christophe Biocca
2014-08-19 17:35 ` Johnathan Corgan
2014-08-19 23:38 ` J Ross Nicoll
2014-08-19 23:39 ` Justus Ranvier
2014-08-19 23:54 ` Gregory Maxwell
2014-08-19 23:40 ` Jeff Garzik
2014-08-20 0:16 ` Peter Todd
2014-08-20 0:21 ` Jeff Garzik [this message]
2014-08-20 0:41 ` Peter Todd
2014-08-20 0:59 ` William Yager
2014-08-20 1:14 ` Peter Todd
2014-08-20 1:19 ` William Yager
2014-08-20 1:27 ` Peter Todd
2014-08-20 0:49 ` Justus Ranvier
2014-08-20 0:57 ` Peter Todd
2014-08-23 16:17 ` xor
2014-08-23 16:50 ` Justus Ranvier
2014-08-23 17:50 ` Troy Benjegerdes
2014-08-23 18:22 ` William Yager
2014-08-23 18:44 ` Mike Hearn
2014-08-23 19:02 ` Luke Dashjr
2014-08-23 22:51 ` Peter Todd
[not found] <c45a638f1e1640fe84bef01d12cda4c3@hotmail.com>
2014-08-20 3:23 ` Un Ix
2014-08-20 5:40 ` Cameron Garnham
2014-08-20 14:37 ` Mike Hearn
2014-08-23 6:39 ` Troy Benjegerdes
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='CAJHLa0PnvpAaTgaUej=1G7CJ9=BYSjEWvXybfEaG9pFJxsM8fQ@mail.gmail.com' \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=justusranvier@riseup.net \
--cc=pete@petertodd.org \
/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