public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Thomas Voegtlin <thomasv1@gmx.de>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 1.9.8 release
Date: Sun, 16 Mar 2014 07:39:11 -0700	[thread overview]
Message-ID: <CAAS2fgQfrnBt3oVNOX4OPJ-3dM+77WMkFDhU-NFBUGEwWSFz-w@mail.gmail.com> (raw)
In-Reply-To: <5325B5BC.3030501@gmx.de>

On Sun, Mar 16, 2014 at 7:31 AM, Thomas Voegtlin <thomasv1@gmx.de> wrote:
> thanks for your feedback!
>
> I was not aware that that implementation was flawed.
> I will see how I can fix that code and get back to you.

It also leaks on the order of 7 bits of data about the message per
message chunk.  I'm also think it's likely that there are some
messages which are just incorrectly decrypted.   ... it's really
screwy and suspect.



  reply	other threads:[~2014-03-16 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 13:24 [Bitcoin-development] Electrum 1.9.8 release Thomas Voegtlin
2014-03-16 13:54 ` Gregory Maxwell
2014-03-16 14:31   ` Thomas Voegtlin
2014-03-16 14:39     ` Gregory Maxwell [this message]
2014-03-16 15:48       ` Thomas Voegtlin

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=CAAS2fgQfrnBt3oVNOX4OPJ-3dM+77WMkFDhU-NFBUGEwWSFz-w@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=thomasv1@gmx.de \
    /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