Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <mh.in.england@gmail.com>) id 1XnBny-0001GB-Vp for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 19:36:15 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.169 as permitted sender) client-ip=209.85.217.169; envelope-from=mh.in.england@gmail.com; helo=mail-lb0-f169.google.com; Received: from mail-lb0-f169.google.com ([209.85.217.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XnBnx-0000fR-Sl for bitcoin-development@lists.sourceforge.net; Sat, 08 Nov 2014 19:36:14 +0000 Received: by mail-lb0-f169.google.com with SMTP id 10so4208937lbg.0 for <bitcoin-development@lists.sourceforge.net>; Sat, 08 Nov 2014 11:36:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.130.132 with SMTP id oe4mr4419688lbb.82.1415475367433; Sat, 08 Nov 2014 11:36:07 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.25.91.147 with HTTP; Sat, 8 Nov 2014 11:36:07 -0800 (PST) In-Reply-To: <CAB+qUq6CxOZpdS+E7rpBmY=4VBiOr845096TUv7koaNXD8gAMg@mail.gmail.com> References: <CANEZrP3Pk3O3uFJtDkO9BfVogbaiWt1SmMrP02fRBpt3TtMrtg@mail.gmail.com> <CAB+qUq6CxOZpdS+E7rpBmY=4VBiOr845096TUv7koaNXD8gAMg@mail.gmail.com> Date: Sat, 8 Nov 2014 20:36:07 +0100 X-Google-Sender-Auth: w3f5IfXXR3o7nBlIFfN5-Xk2IMc Message-ID: <CANEZrP3EWXDwXefzeFfEYS=KBVPLnu-dNxufAZQnednmhFPBWw@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Chris Pacia <ctpacia@gmail.com> Content-Type: multipart/alternative; boundary=047d7b3a84c076dfe305075e0a83 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1XnBnx-0000fR-Sl Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Update on mobile 2-factor wallets 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: Sat, 08 Nov 2014 19:36:15 -0000 --047d7b3a84c076dfe305075e0a83 Content-Type: text/plain; charset=UTF-8 > > I am familiar with the Princeton threshold signature but I was under the > impression a single key needed to be generated on a single device then > split and distributed. > > Does this scheme work the same way? > No, it doesn't. Neither device ever sees as master private key. --047d7b3a84c076dfe305075e0a83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex"><p dir=3D"ltr">I am familiar with the Princeton = threshold signature but I was under the impression a single key needed to b= e generated on a single device then split and distributed.</p> <p dir=3D"ltr">Does this scheme work the same way?</p></blockquote><div>No,= it doesn't. Neither device ever sees as master private key.</div></div= ></div></div> --047d7b3a84c076dfe305075e0a83--