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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YILI1-0004OM-Ob for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:00:01 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.177 as permitted sender) client-ip=209.85.212.177; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f177.google.com; Received: from mail-wi0-f177.google.com ([209.85.212.177]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YILI0-0000Sk-Io for bitcoin-development@lists.sourceforge.net; Mon, 02 Feb 2015 18:00:01 +0000 Received: by mail-wi0-f177.google.com with SMTP id r20so16820248wiv.4 for ; Mon, 02 Feb 2015 09:59:54 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.207.10 with SMTP id ls10mr26857523wic.7.1422899994475; Mon, 02 Feb 2015 09:59:54 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.11 with HTTP; Mon, 2 Feb 2015 09:59:54 -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 18:59:54 +0100 X-Google-Sender-Auth: HXsdESQSizQERakkw9E9QpZ_O3Y Message-ID: From: Mike Hearn To: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= Content-Type: multipart/alternative; boundary=001a11c3f51ab8c6cb050e1eb87c 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: 1YILI0-0000Sk-Io 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:00:01 -0000 --001a11c3f51ab8c6cb050e1eb87c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We're way ahead of you guys ;) On Mon, Feb 2, 2015 at 6:54 PM, Martin Habov=C5=A1tiak < martin.habovstiak@gmail.com> 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 key i= s > placed in cold storage and anther sent to a third-party. > BitGo, CryptoCorp and (slight variant) GreenAddress all offer this model. --001a11c3f51ab8c6cb050e1eb87c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We're way ahead of you guys ;)

On Mon, Feb 2, 2015 at 6:54 PM, Marti= n Habov=C5=A1tiak <martin.habovstiak@gmail.com> wr= ote:
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/ =C2= =A0 =C2=A0 =C2=A0- does this already, currently in alpha
=C2=A0
> It should be po= ssible to use multisig wallets to protect against malware.=C2=A0 For exampl= e, a user could generate a wallet with 3 keys and require a transaction tha= t has been signed by 2 of those keys.=C2=A0 One key is placed in cold stora= ge and anther sent to a third-party.

<= /div>
BitGo, CryptoCorp and (slight variant) GreenAddress all offer thi= s model.=C2=A0
--001a11c3f51ab8c6cb050e1eb87c--