From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YILKh-0003o3-9d for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:02:47 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.53 as permitted sender) client-ip=209.85.192.53; envelope-from=martin.habovstiak@gmail.com; helo=mail-qg0-f53.google.com; Received: from mail-qg0-f53.google.com ([209.85.192.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YILKf-0000YC-A5 for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:02:47 +0000 Received: by mail-qg0-f53.google.com with SMTP id a108so48617426qge.12 for ; Mon, 02 Feb 2015 10:02:39 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.229.70.133 with SMTP id d5mr763445qcj.2.1422900159765; Mon, 02 Feb 2015 10:02:39 -0800 (PST) Received: by 10.140.19.18 with HTTP; Mon, 2 Feb 2015 10:02:39 -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:02:39 +0100 Message-ID: From: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= To: Mike Hearn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 (martin.habovstiak[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: 1YILKf-0000YC-A5 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:02:47 -0000 Do you have anything that is NOT some web application? 2015-02-02 18:59 GMT+01:00 Mike Hearn : > We're way ahead of you guys ;) > > On Mon, Feb 2, 2015 at 6:54 PM, Martin Habov=C5=A1tiak > wrote: >> >> Good idea. I think this could be even better: >> >> instead of using third party, send partially signed TX from computer >> to smartphone. In case, you are paranoid, make 3oo5 address made of >> two cold storage keys, one on desktop/laptop, one on smartphone, one >> using third party. > > > https://www.bitcoinauthenticator.org/ - does this already, currently= in > alpha > >> >> > It should be possible to use multisig wallets to protect against >> > malware. For example, a user could generate a wallet with 3 keys and >> > require a transaction that has been signed by 2 of those keys. One ke= y is >> > placed in cold storage and anther sent to a third-party. > > > BitGo, CryptoCorp and (slight variant) GreenAddress all offer this model.