Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WLBix-0006a6-9N for bitcoin-development@lists.sourceforge.net; Wed, 05 Mar 2014 13:19:03 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of me.com designates 17.172.220.236 as permitted sender) client-ip=17.172.220.236; envelope-from=jeanpaulkogelman@me.com; helo=st11p02mm-asmtp001.mac.com; Received: from st11p02mm-asmtp001.mac.com ([17.172.220.236]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1WLBiw-0006F2-C5 for bitcoin-development@lists.sourceforge.net; Wed, 05 Mar 2014 13:19:03 +0000 Received: from [172.65.103.42] (unknown [218.188.76.249]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N1Y008T9SYXCS80@st11p02mm-asmtp001.mac.com> for bitcoin-development@lists.sourceforge.net; Wed, 05 Mar 2014 13:18:37 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-03-05_05:2014-03-05, 2014-03-05, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=2 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1401130000 definitions=main-1403050041 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (1.0) From: Jean-Paul Kogelman X-Mailer: iPhone Mail (11B651) In-reply-to: Date: Wed, 05 Mar 2014 21:18:31 +0800 Content-transfer-encoding: quoted-printable Message-id: References: To: Pieter Wuille X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1WLBiw-0006F2-C5 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] New side channel attack that can recover Bitcoin keys 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: Wed, 05 Mar 2014 13:19:03 -0000 > On Mar 5, 2014, at 8:56 PM, Pieter Wuille wrote:= >=20 >> On Wed, Mar 5, 2014 at 1:49 PM, Mike Hearn wrote: >> I am not currently aware of any efforts to make OpenSSL's secp256k1 >> implementation completely side channel free in all aspects. Also, >> unfortunately many people have reimplemented ECDSA themselves and even if= >> OpenSSL gets fixed, the custom implementations probably won't. >=20 > As far as I know, judging from the implementation, there is hardly any > effort to try to prevent timing attacks. >=20 Is it safe to assume that this is also true for your secp256k1 implementatio= n? jp > --=20 > Pieter >=20 > --------------------------------------------------------------------------= ---- > Subversion Kills Productivity. Get off Subversion & Make the Move to Perfo= rce. > With Perforce, you get hassle-free workflows. Merge that actually works.=20= > Faster operations. Version large binaries. Built-in WAN optimization and t= he > freedom to use Git, Perforce or both. Make the move to Perforce. > http://pubads.g.doubleclick.net/gampad/clk?id=3D122218951&iu=3D/4140/ostg.= clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development