public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: xor <xor@freenetproject.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Proposal: Encrypt bitcoin messages
Date: Sat, 23 Aug 2014 18:17:54 +0200	[thread overview]
Message-ID: <1569765.oHsHtFYAhh@1337h4x0r> (raw)
In-Reply-To: <CAJHLa0ORxgQrkc4oiqSa3NdNHLU-0pmZDLjXUSpBKWBsBWTgcQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On Tuesday, August 19, 2014 07:40:39 PM Jeff Garzik wrote:
> Encryption is of little value if you may deduce the same information
> by observing packet sizes and timings.

Instead of spawning a discussion whether this aspect is a reason to NOT 
encrypt, you should do the obvious:

Fix that as well. X being broken is not a reason for not fixing Y.
Pad the then encrypted packets with random bytes. The fact that they are 
encrypted makes them look like random data already, so the padding will not be 
distinguishable from the rest.
Also, add some random bias to their timing.

And besides: It would be nice if everyone could acknowledge that making 
Bitcoin as anonymous as possible is a natural desire. People demanding you to 
do this is bound to happen over and over again until you do it :) So just get 
on with it instead of postponing it due to doubts.

There is Tor, there is Freenet, and there are other anonymous P2P networks, 
and they can help you do get it done - the said problems have been well-known 
there for quite some time and people have thought about how to solve them.

Greetings,
	xor, a developer of https://freenetproject.org

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-08-23 16:18 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
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 [this message]
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=1569765.oHsHtFYAhh@1337h4x0r \
    --to=xor@freenetproject.org \
    --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