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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
Return-Path: <fred_savage2003@hotmail.co.uk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 9DA05CF7
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 4 Jul 2018 18:08:46 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from EUR02-HE1-obe.outbound.protection.outlook.com
(mail-oln040092068023.outbound.protection.outlook.com [40.92.68.23])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C06E0780
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 4 Jul 2018 18:08:45 +0000 (UTC)
Received: from HE1EUR02FT059.eop-EUR02.prod.protection.outlook.com
(10.152.10.58) by HE1EUR02HT038.eop-EUR02.prod.protection.outlook.com
(10.152.11.250) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.906.15;
Wed, 4 Jul 2018 18:08:43 +0000
Received: from DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM (10.152.10.54) by
HE1EUR02FT059.mail.protection.outlook.com (10.152.11.25) with Microsoft
SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
15.20.906.15 via Frontend Transport; Wed, 4 Jul 2018 18:08:43 +0000
Received: from DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM
([fe80::51da:8791:dbbe:e34f]) by
DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM
([fe80::51da:8791:dbbe:e34f%8]) with mapi id 15.20.0906.026;
Wed, 4 Jul 2018 18:08:43 +0000
From: fred savage <fred_savage2003@hotmail.co.uk>
To: Luke Dashjr <luke@dashjr.org>, Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: [bitcoin-dev] [Lightning-dev] BIP sighash_noinput
Thread-Index: AQHUEselD0WWJh1tD0mLalZbedKWy6R/Xhk1
Date: Wed, 4 Jul 2018 18:08:43 +0000
Message-ID: <DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410@DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM>
References: <871sewirni.fsf@gmail.com>
<CAAS2fgS-_D7aBcDf_nAbuREBxv65zYMr60-1YqCnx-esvRVfEg@mail.gmail.com>,
<201807031213.51127.luke@dashjr.org>
In-Reply-To: <201807031213.51127.luke@dashjr.org>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:163D7866CDDFEBA84D6526DE83ADA3AFB298D1564426A8C8EBCB7FE61B6649CD;
UpperCasedChecksum:7C67D92A902335EFC06D014D2534648F77DA17697941FBD049965C186FF1E1D2;
SizeAsReceived:7318; Count:46
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [nFQQujMsO8PLnJ9ixasjK6SH/Teuzf5j9m7yZPwnR+S+5lHStI4SlHyKhXQzJf40]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT038;
7:piRx6yVEFDsLZIKWlmBbgloXI1M1FnGco6Wz8m7+XcXoyMW4t4DGFwJJ/hry9Ob3bvza9TXfAQ5cvDmEguDW4A6lLD/KBnAo8JzjzHnJRMFJ+vdFli7fOGHJxXOT+guNMGEQEl8iTIRHRSWpSJdR/oikjNhhKQDFukY7FyYVC+pYO7p10aJNl3y/R2aCc5YAAi4PjGeNxEe5Ig3Rocb7Z0grR3Jzw/nTPCvMLMAw53TkCNlwrhstPma92fTiF1f3
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125500)(1603101448)(1701031045);
SRVR:HE1EUR02HT038;
x-ms-traffictypediagnostic: HE1EUR02HT038:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031);
SRVR:HE1EUR02HT038; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT038;
x-forefront-prvs: 0723A02764
x-forefront-antispam-report: SFV:NSPM;
SFS:(7070007)(199004)(189003)(19627405001)(97736004)(68736007)(102836004)(104016004)(105586002)(25786009)(74482002)(5660300001)(6506007)(82202002)(6306002)(46003)(9686003)(54896002)(73972006)(86362001)(6436002)(236005)(33656002)(6606003)(486006)(74316002)(110136005)(11346002)(55016002)(6346003)(476003)(446003)(6246003)(8676002)(8936002)(2900100001)(81156014)(76176011)(14454004)(5250100002)(966005)(7696005)(99286004)(606006)(14444005)(106356001)(229853002)(86152003)(256004)(46252003);
DIR:OUT; SFP:1901; SCL:1; SRVR:HE1EUR02HT038;
H:DB6PR1001MB1302.EURPRD10.PROD.OUTLOOK.COM; FPR:; SPF:None;
PTR:InfoNoRecords; A:1; MX:1; LANG:;
received-spf: None (protection.outlook.com: hotmail.co.uk does not designate
permitted sender hosts)
authentication-results: spf=none (sender IP is )
smtp.mailfrom=fred_savage2003@hotmail.co.uk;
x-microsoft-antispam-message-info: utl7/l/3wd1QXGqbfyAZjC7m99Ses0TEkcQBbMC/MPdwT4zZt/6NjH8UWNjydJ/LmCUc5kFfc0At/r4DYzYl/hKfbPrdq6P3ZFodPEEyF/rBk2nC45a7lCVlVP6J8wrd+JlBDvSUH75v8NwGbVgiKFzEEPs45kKEYIgUt3wDpl1ADlxCfzl4F7zcHWbn+S2Q47dbAh9VYnx336x4XyqwRduoC7Fgxe8QWBCUx2nC2QY=
Content-Type: multipart/alternative;
boundary="_000_DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410DB6PR1001MB1302_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-Network-Message-Id: 17555a80-08df-4a16-3df2-08d5e1d92dad
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 54485d23-c432-40fe-8436-6091d627118c
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jul 2018 18:08:43.2453 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT038
X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,
FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 05 Jul 2018 07:57:46 +0000
Subject: Re: [bitcoin-dev] [Lightning-dev] BIP sighash_noinput
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2018 18:08:46 -0000
--_000_DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410DB6PR1001MB1302_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
you cannot specifically NOT support addrss reuse. on a blockchain where peo=
ple can send you funds without your permission required to send you funds. =
so ALWAYS expect multiple payments to the same address
________________________________
From: bitcoin-dev-bounces@lists.linuxfoundation.org <bitcoin-dev-bounces@li=
sts.linuxfoundation.org> on behalf of Luke Dashjr via bitcoin-dev <bitcoin-=
dev@lists.linuxfoundation.org>
Sent: 03 July 2018 12:13:44
To: lightning-dev@lists.linuxfoundation.org
Cc: Bitcoin Protocol Discussion
Subject: Re: [bitcoin-dev] [Lightning-dev] BIP sighash_noinput
On Monday 02 July 2018 18:11:54 Gregory Maxwell wrote:
> I know it seems kind of silly, but I think it's somewhat important
> that the formal name of this flag is something like
> "SIGHASH_REPLAY_VULNERABLE" or likewise or at least
> "SIGHASH_WEAK_REPLAYABLE". This is because noinput is materially
> insecure for traditional applications where a third party might pay to
> an address a second time, and should only be used in special protocols
> which make that kind of mistake unlikely.
I don't agree. Address reuse is undefined behaviour. Nobody should assume i=
t
is safe or works.
I intend to possibly use SIGHASH_NOINPUT for ordinary Bitcoin transactions =
in
a wallet I am writing, which explicitly does not support address reuse.
Luke
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--_000_DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410DB6PR1001MB1302_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">you cannot specifically NOT suppo=
rt addrss reuse. on a blockchain where people can send you funds without yo=
ur permission required to send you funds. so ALWAYS expect multiple payment=
s to the same address<br>
</p>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> bitcoin-dev-bounces@l=
ists.linuxfoundation.org <bitcoin-dev-bounces@lists.linuxfoundation.org&=
gt; on behalf of Luke Dashjr via bitcoin-dev <bitcoin-dev@lists.linuxfou=
ndation.org><br>
<b>Sent:</b> 03 July 2018 12:13:44<br>
<b>To:</b> lightning-dev@lists.linuxfoundation.org<br>
<b>Cc:</b> Bitcoin Protocol Discussion<br>
<b>Subject:</b> Re: [bitcoin-dev] [Lightning-dev] BIP sighash_noinput</font=
>
<div> </div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">On Monday 02 July 2018 18:11:54 Gregory Maxwell wr=
ote:<br>
> I know it seems kind of silly, but I think it's somewhat important<br>
> that the formal name of this flag is something like<br>
> "SIGHASH_REPLAY_VULNERABLE" or likewise or at least<br>
> "SIGHASH_WEAK_REPLAYABLE". This is because noinput is materi=
ally<br>
> insecure for traditional applications where a third party might pay to=
<br>
> an address a second time, and should only be used in special protocols=
<br>
> which make that kind of mistake unlikely. <br>
<br>
I don't agree. Address reuse is undefined behaviour. Nobody should assume i=
t <br>
is safe or works.<br>
<br>
I intend to possibly use SIGHASH_NOINPUT for ordinary Bitcoin transactions =
in <br>
a wallet I am writing, which explicitly does not support address reuse.<br>
<br>
Luke<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
bitcoin-dev@lists.linuxfoundation.org<br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">=
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
</div>
</span></font></div>
</body>
</html>
--_000_DB6PR1001MB1302B5C6237A8A4DBE0CB6A4DE410DB6PR1001MB1302_--
|
