From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YILgY-0005dT-Mk for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:25:22 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.170 as permitted sender) client-ip=74.125.82.170; envelope-from=mh.in.england@gmail.com; helo=mail-we0-f170.google.com; Received: from mail-we0-f170.google.com ([74.125.82.170]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YILgW-0000Iq-RZ for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:25:22 +0000 Received: by mail-we0-f170.google.com with SMTP id w55so35263825wes.1 for ; Mon, 02 Feb 2015 10:25:14 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.60.77 with SMTP id f13mr45429859wjr.105.1422901514751; Mon, 02 Feb 2015 10:25:14 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Mon, 2 Feb 2015 10:25:14 -0800 (PST) In-Reply-To: References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com> <54CE3816.6020505@bitwatch.co> <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com> Date: Mon, 2 Feb 2015 19:25:14 +0100 X-Google-Sender-Auth: flcrAiiU5oacbBuUDz1w13w2STw Message-ID: From: Mike Hearn To: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= Content-Type: multipart/alternative; boundary=047d7b86db8a565743050e1f1372 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: 1YILgW-0000Iq-RZ 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:25:22 -0000 --047d7b86db8a565743050e1f1372 Content-Type: text/plain; charset=UTF-8 > > Do you have anything that is NOT some web application? > 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. It's done in the same way as Lighthouse, so it runs Win/Mac/Linux on desktop and Android on mobile. 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. --047d7b86db8a565743050e1f1372 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Do you have anything that is NOT some web applic= ation?

Bitcoin Authenticator is a deskt= op app+mobile app pair. It pairs with your phone over wifi, cloud push, may= be Bluetooth as well. I forget exactly.=C2=A0

It&#= 39;s done in the same way as Lighthouse, so it runs Win/Mac/Linux on deskto= p and Android on mobile.

It could be adapted to us= e BitGo as a third party key holder with SMS authenticator relatively easil= y, 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 w= eb app.
--047d7b86db8a565743050e1f1372--