1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1WPCDe-0002CY-M7
for bitcoin-development@lists.sourceforge.net;
Sun, 16 Mar 2014 14:39:19 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.48 as permitted sender)
client-ip=209.85.215.48; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f48.google.com;
Received: from mail-la0-f48.google.com ([209.85.215.48])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WPCDd-0000Zu-Us
for bitcoin-development@lists.sourceforge.net;
Sun, 16 Mar 2014 14:39:18 +0000
Received: by mail-la0-f48.google.com with SMTP id gf5so2949306lab.21
for <bitcoin-development@lists.sourceforge.net>;
Sun, 16 Mar 2014 07:39:11 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.170.234 with SMTP id ap10mr12564198lbc.23.1394980751464;
Sun, 16 Mar 2014 07:39:11 -0700 (PDT)
Received: by 10.112.184.226 with HTTP; Sun, 16 Mar 2014 07:39:11 -0700 (PDT)
In-Reply-To: <5325B5BC.3030501@gmx.de>
References: <5325A61B.6050802@gmx.de>
<CAAS2fgR766pjD43bZawuJH9VQ7S0dQRGY9HetOuj9HR3Pk=1_A@mail.gmail.com>
<5325B5BC.3030501@gmx.de>
Date: Sun, 16 Mar 2014 07:39:11 -0700
Message-ID: <CAAS2fgQfrnBt3oVNOX4OPJ-3dM+77WMkFDhU-NFBUGEwWSFz-w@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Thomas Voegtlin <thomasv1@gmx.de>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WPCDd-0000Zu-Us
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 1.9.8 release
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 16 Mar 2014 14:39:19 -0000
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.
|
