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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YILqy-0005TK-H5 for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:36:08 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.175 as permitted sender) client-ip=209.85.216.175; envelope-from=brian.erdelyi@gmail.com; helo=mail-qc0-f175.google.com; Received: from mail-qc0-f175.google.com ([209.85.216.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YILqx-00055n-Pz for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:36:08 +0000 Received: by mail-qc0-f175.google.com with SMTP id c9so31589969qcz.6 for ; Mon, 02 Feb 2015 10:36:02 -0800 (PST) X-Received: by 10.224.30.145 with SMTP id u17mr44113227qac.46.1422902162234; Mon, 02 Feb 2015 10:36:02 -0800 (PST) Received: from [192.168.1.58] ([64.147.83.112]) by mx.google.com with ESMTPSA id g100sm18997106qge.1.2015.02.02.10.36.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 10:36:01 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) From: Brian Erdelyi In-Reply-To: Date: Mon, 2 Feb 2015 14:35:59 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <57186618-F010-42E6-A757-B617C4001B5B@gmail.com> References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com> <54CE3816.6020505@bitwatch.co> <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com> To: Mike Hearn X-Mailer: Apple Mail (2.2070.6) X-Spam-Score: -1.3 (-) 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 (brian.erdelyi[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 0.3 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YILqx-00055n-Pz Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Proposal to address Bitcoin malware 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: Mon, 02 Feb 2015 18:36:08 -0000 > Bitcoin Authenticator is a desktop app+mobile app pair. It pairs with = your phone over wifi, cloud push, maybe Bluetooth as well. I forget = exactly.=20 >=20 > It's done in the same way as Lighthouse, so it runs Win/Mac/Linux on = desktop and Android on mobile. >=20 > It could be adapted to use BitGo as a third party key holder with SMS = authenticator relatively easily, I think. We did the bulk of all the = needed work last year as part of the bitcoinj multisig work. Then you'd = have a server involved, but not a web app. I really like the concept of Bitcoin Authenticator and think it=E2=80=99s = exactly what I was describing (without a third-party). I think it=E2=80=99s a bit confusing when they describe Bitcoin = Authenticator as 2FA. I think it may be more accurate to describe it as = out of band transaction verification/signing or dual transaction = signing. Regardless, it=E2=80=99s very exciting to see others are = thinking about this too. Brian Erdelyi=