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
73
74
75
76
77
78
79
80
81
82
83
|
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 <thomas@thomaszander.se>) id 1Xdwpw-0003bZ-6y
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Oct 2014 07:48:04 +0000
X-ACL-Warn:
Received: from mail1.bemta3.messagelabs.com ([195.245.230.167])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Xdwpu-0001jN-Dz
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Oct 2014 07:48:04 +0000
Received: from [85.158.138.179:29644] by server-7.bemta-3.messagelabs.com id
0E/E1-01084-A60DC345; Tue, 14 Oct 2014 07:27:38 +0000
X-Env-Sender: thomas@thomaszander.se
X-Msg-Ref: server-10.tower-169.messagelabs.com!1413271657!9388817!1
X-Originating-IP: [83.145.56.68]
X-StarScan-Received:
X-StarScan-Version: 6.12.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7230 invoked from network); 14 Oct 2014 07:27:38 -0000
Received: from unknown (HELO mail.infront.no) (83.145.56.68)
by server-10.tower-169.messagelabs.com with AES128-SHA encrypted SMTP;
14 Oct 2014 07:27:38 -0000
Received: from SE8EX13-MBX01.osl.infront.as (10.234.180.15) by
SE8TMG.osl.infront.as (10.234.180.35) with Microsoft SMTP Server (TLS)
id 14.3.158.1; Tue, 14 Oct 2014 09:27:37 +0200
Received: from SE8EX13-CAS.osl.infront.as (10.234.180.10) by
SE8EX13-MBX01.osl.infront.as (10.234.180.15) with Microsoft SMTP Server
(TLS) id 15.0.775.38; Tue, 14 Oct 2014 09:27:36 +0200
Received: from debian.localnet (10.234.92.34) by SE8EX13-CAS.osl.infront.as
(10.234.180.11) with Microsoft SMTP Server (TLS) id 15.0.775.38 via
Frontend Transport; Tue, 14 Oct 2014 09:27:36 +0200
From: Thomas Zander <thomas@thomaszander.se>
To: <bitcoin-development@lists.sourceforge.net>
Date: Tue, 14 Oct 2014 09:27:36 +0200
User-Agent: KMail/1.13.7 (Linux/3.2.0-4-486; KDE/4.8.4; i686; ; )
References: <CAPg+sBjbeAaTmEvqrHHU4Mb45VPyRvFxdRzz1S6+-t7ep20ZtQ@mail.gmail.com>
In-Reply-To: <CAPg+sBjbeAaTmEvqrHHU4Mb45VPyRvFxdRzz1S6+-t7ep20ZtQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-ID: <201410140927.36252.thomas@thomaszander.se>
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
X-Headers-End: 1Xdwpu-0001jN-Dz
Subject: Re: [Bitcoin-development] Malleable booleans
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: Tue, 14 Oct 2014 07:48:04 -0000
On Tuesday 14. October 2014 04.34.16 Pieter Wuille wrote:
> This means that scripts that use booleans as inputs will be inherently
> malleable.
I've ran into this issue in C++ often enough,
a funny example is assigning "2" to a native c++ bool and then you can do a
if (myBool == true)
else if (myBool == false)
and neither of them will hit.
> I
> would like to change BIP62 to also state that interpreted booleans
> must be of minimal encoded size (in addition to numbers).
What about rejecting a script where a bool is not explicitly zero or one?
--
Thomas Zander
|
