Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2C29292B for ; Wed, 6 Jun 2018 00:43:34 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from outmail149056.authsmtp.com (outmail149056.authsmtp.com [62.13.149.56]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E235B73A for ; Wed, 6 Jun 2018 00:43:32 +0000 (UTC) Received: from mail-c245.authsmtp.com (mail-c245.authsmtp.com [62.13.128.245]) by punt24.authsmtp.com. (8.15.2/8.15.2) with ESMTP id w560hUAi004732; Wed, 6 Jun 2018 01:43:30 +0100 (BST) (envelope-from user@petertodd.org) Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com [52.5.185.120]) (authenticated bits=0) by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id w560hScx001326 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Jun 2018 01:43:29 +0100 (BST) (envelope-from user@petertodd.org) Received: from [127.0.0.1] (localhost [127.0.0.1]) by petertodd.org (Postfix) with ESMTPSA id C6EEF400D0; Wed, 6 Jun 2018 00:43:27 +0000 (UTC) Received: by localhost (Postfix, from userid 1000) id 9237022043; Tue, 5 Jun 2018 20:43:26 -0400 (EDT) Date: Tue, 5 Jun 2018 20:43:26 -0400 From: Peter Todd To: Chris Stewart , Bitcoin Protocol Discussion Message-ID: <20180606004326.hpd3tmkjhdzclf2g@petertodd.org> References: <9FC9FA73-9572-48AF-9590-68F0D298D6A0@xbt.hk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gdqb4ejucibu776b" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-Server-Quench: a1c8e2ae-6922-11e8-a283-9cb654bb2504 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZIVwkA IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgQUEkAaAgsB Am4bW1VeVF57W2o7 bghPaBtcak9QXgdq T0pMXVMcUwBuAURi VVYeUhhxdQMIfndw ZggzXyNTCUYrIFt7 S0xWCGwHMG99OWIX U11RJFFSdQcYLB1A alQxNiYHcQ5VPz4z GA41ejw8IwAXBCVO SwUJKk1aQEAQEzUh XR1KAC4iVUoLDx4S ADwPEX4rJ2c3HWEf WQAA X-Authentic-SMTP: 61633532353630.1039:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 52.5.185.120/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Disallow insecure use of SIGHASH_SINGLE X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 00:43:34 -0000 --gdqb4ejucibu776b Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 05, 2018 at 07:17:52PM -0500, Chris Stewart via bitcoin-dev wro= te: > Do you have any thoughts on expanding this to SIGHASH_NONE? Perhaps someo= ne > else on the dev list can enlighten me, but is there a current use case for > SIGHASH_NONE that would suffer from it being non standard? SIGHASH_NONE is important as it's the only way that a multisig signers can relinquish the need for them to sign without giving up the private key. FWIW the SIGHASH_SINGLE bug can be used in similar ways too. --=20 https://petertodd.org 'peter'[:-1]@petertodd.org --gdqb4ejucibu776b Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEFcyURjhyM68BBPYTJIFAPaXwkfsFAlsXLigACgkQJIFAPaXw kft4xQgAobpH/F7r1eZ0871mGkmxgh2VRjVcDHReckljU9Kptr7up0jNYoBHp50y HE/esN+chqZqKfKBNgDPtLhk8EsgIVhSv1k5CTgWbQy/w5bQoPJH92jY4N93ywmo KxzM8GfnL2x6cfTw5BlEZHEvo9a5MyrVSTZeZ3Cn5Y1dvlU2YObSb11cYkLlRCn1 iVGZwrYZtppcgyCK8pl4DDjmtg7aL8ynFGzFmZqYqSpT1yB0vkQJSxFuwHjEtmkA WbT9iflwGNDuAhwTTbjG56pF8d/Pmu8+f7hI/AgK7IKu9KhhsGSrXagQDWSO6+hP PqvlFivxk5zmMTsJfooCgUJlf4lw1g== =ScKE -----END PGP SIGNATURE----- --gdqb4ejucibu776b--