diff options
| author | Martin Habovštiak <martin.habovstiak@gmail.com> | 2015-02-02 19:02:39 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-02-02 18:02:47 +0000 |
| commit | 0bbf2ff04015b5ac6211096c0c56f44daad73972 (patch) | |
| tree | 18667aa6f879bd4849b1e5a0dbb4848f60aa4a2f /c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f | |
| parent | 74a97170277f8567c4f989e076214376f27cc301 (diff) | |
| download | pi-bitcoindev-0bbf2ff04015b5ac6211096c0c56f44daad73972.tar.gz pi-bitcoindev-0bbf2ff04015b5ac6211096c0c56f44daad73972.zip | |
Re: [Bitcoin-development] Proposal to address Bitcoin malware
Diffstat (limited to 'c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f')
| -rw-r--r-- | c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f | 95 |
1 files changed, 95 insertions, 0 deletions
diff --git a/c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f b/c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f new file mode 100644 index 000000000..0003dbfd3 --- /dev/null +++ b/c2/0eaf696bd9d322f72776a7f6dfbc8722d0a57f @@ -0,0 +1,95 @@ +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 <martin.habovstiak@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>; + 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: <CANEZrP0QjPm+TTgV9Fh84vt2zLaGp0R2Wt2ZL2ZXYhxzOFPHVA@mail.gmail.com> +References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com> + <54CE3816.6020505@bitwatch.co> + <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com> + <CALkkCJbk0czFj5mdMB6_0+Umw5V-fo-4tdBHgvg92zhyRZWiYQ@mail.gmail.com> + <CANEZrP0QjPm+TTgV9Fh84vt2zLaGp0R2Wt2ZL2ZXYhxzOFPHVA@mail.gmail.com> +Date: Mon, 2 Feb 2015 19:02:39 +0100 +Message-ID: <CALkkCJYuM_T=_nfBOCF4S8XhVecUZA0ug==Y_n+qdFpb-F628g@mail.gmail.com> +From: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= <martin.habovstiak@gmail.com> +To: Mike Hearn <mike@plan99.net> +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 <bitcoin-development@lists.sourceforge.net> +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: <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: 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 <mike@plan99.net>: +> 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 ke= +y is +>> > placed in cold storage and anther sent to a third-party. +> +> +> BitGo, CryptoCorp and (slight variant) GreenAddress all offer this model. + + |