From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YIi0X-0005UM-6Z for bitcoin-development@lists.sourceforge.net; Tue, 03 Feb 2015 18:15:29 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.173 as permitted sender) client-ip=209.85.213.173; envelope-from=pieter.wuille@gmail.com; helo=mail-ig0-f173.google.com; Received: from mail-ig0-f173.google.com ([209.85.213.173]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YIi0R-0005gs-Ug for bitcoin-development@lists.sourceforge.net; Tue, 03 Feb 2015 18:15:29 +0000 Received: by mail-ig0-f173.google.com with SMTP id a13so28614158igq.0 for ; Tue, 03 Feb 2015 10:15:18 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.28.8 with SMTP id x8mr19410323igg.19.1422987318632; Tue, 03 Feb 2015 10:15:18 -0800 (PST) Received: by 10.50.20.229 with HTTP; Tue, 3 Feb 2015 10:15:18 -0800 (PST) In-Reply-To: References: <87egqnwt7g.fsf@rustcorp.com.au> Date: Tue, 3 Feb 2015 10:15:18 -0800 Message-ID: From: Pieter Wuille To: Wladimir Content-Type: text/plain; charset=ISO-8859-1 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 (pieter.wuille[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: 1YIi0R-0005gs-Ug Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [softfork proposal] Strict DER signatures X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 18:15:29 -0000 On Tue, Feb 3, 2015 at 4:00 AM, Wladimir wrote: >> One way to do that is to just - right now - add a patch to 0.10 to >> make those non-standard. This requires another validation flag, with a >> bunch of switching logic. >> >> The much simpler alternative is just adding this to BIP66's DERSIG >> right now, which is a one-line change that's obviously softforking. Is >> anyone opposed to doing so at this stage? > > Not opposed, but is kind of late for 0.10, I had hoped to tag rc4 today. I understand it's late, which is also why I ask for opinions. It's also not a priority, but if we release 0.10 without, it will first need a cycle of making this non-standard, and then in a further release doing a second softfork to enforce it. It's a 2-line change; see #5743. -- Pieter