summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Voskuil <eric@voskuil.org>2015-02-02 11:05:57 -0700
committerbitcoindev <bitcoindev@gnusha.org>2015-02-02 18:42:11 +0000
commit4c1235cb76c3f7256988f516347519535b2cd349 (patch)
treea0a8fbf610ec189a697c6636e812d4166eb23fa6
parent73449e8a730ba572159400f7398320363c03c397 (diff)
downloadpi-bitcoindev-4c1235cb76c3f7256988f516347519535b2cd349.tar.gz
pi-bitcoindev-4c1235cb76c3f7256988f516347519535b2cd349.zip
Re: [Bitcoin-development] Proposal to address Bitcoin malware
-rw-r--r--4d/f8cd54d54f7c073b26acff1c8fbf684cb7d37b109
1 files changed, 109 insertions, 0 deletions
diff --git a/4d/f8cd54d54f7c073b26acff1c8fbf684cb7d37b b/4d/f8cd54d54f7c073b26acff1c8fbf684cb7d37b
new file mode 100644
index 000000000..202c603ef
--- /dev/null
+++ b/4d/f8cd54d54f7c073b26acff1c8fbf684cb7d37b
@@ -0,0 +1,109 @@
+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <eric@voskuil.org>) id 1YILwp-000890-MI
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 02 Feb 2015 18:42:11 +0000
+X-ACL-Warn:
+Received: from mail-pa0-f50.google.com ([209.85.220.50])
+ by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1YILwo-0000sS-Hl
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 02 Feb 2015 18:42:11 +0000
+Received: by mail-pa0-f50.google.com with SMTP id rd3so85512090pab.9
+ for <bitcoin-development@lists.sourceforge.net>;
+ Mon, 02 Feb 2015 10:42:04 -0800 (PST)
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=1e100.net; s=20130820;
+ h=x-gm-message-state:references:mime-version:in-reply-to:content-type
+ :content-transfer-encoding:message-id:cc:from:subject:date:to;
+ bh=Fs10Tu9Un19RNRXLpr8jai5lEGRY2P0eIJkm4955TxQ=;
+ b=ZxtVkc5nVQDIQC2R4yFFzIpqvvFU/eNelYkm1vgUGB7VImIpxhyOg7pSWI56Nm5zCX
+ uDc5rEYbWehX13ygQKGi9RIFTGzS9KHhOQ9l0HtXAVjKxmmcOyijkDFVt1wbs7EVyk6i
+ RC7uVOI+5nHjTSDSHGVewZdV6JiMja/MmT3akJpUZuZdqNPk/c0ln2Aay5tUaevr+FkF
+ 46OQxo2bugaf3E8KZJymxGAVRjbxuf6K9qRnpTCR8L20pHm0mxobVZLf1+5tRKSV/7ef
+ 0d8XERv86E/dLac01236wChnHheyiy6Wp+yDDgaxs103dwf+K+9/QYkGwjSqnOVQN6dh
+ KFJg==
+X-Gm-Message-State: ALoCoQlaUXccnPOhGuo6qb7O/MCNDys84XffWQx8Nei9gvg/+tMieQP1JZaj+C9S9OBBPhyJhNup
+X-Received: by 10.68.189.71 with SMTP id gg7mr728416pbc.21.1422900704579;
+ Mon, 02 Feb 2015 10:11:44 -0800 (PST)
+Received: from [10.125.42.145] (mobile-166-171-121-213.mycingular.net.
+ [166.171.121.213]) by mx.google.com with ESMTPSA id
+ ox2sm19508025pdb.21.2015.02.02.10.11.43
+ (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
+ Mon, 02 Feb 2015 10:11:44 -0800 (PST)
+References: <27395C55-CF59-4E65-83CA-73F903272C5F@gmail.com>
+ <54CE3816.6020505@bitwatch.co>
+ <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com>
+Mime-Version: 1.0 (1.0)
+In-Reply-To: <68C03646-02E7-43C6-9B73-E4697F3AA5FD@gmail.com>
+Content-Type: text/plain;
+ charset=us-ascii
+Content-Transfer-Encoding: quoted-printable
+Message-Id: <05590A33-1802-4C15-91C0-8777ACD8440B@voskuil.org>
+X-Mailer: iPhone Mail (12B440)
+From: Eric Voskuil <eric@voskuil.org>
+Date: Mon, 2 Feb 2015 11:05:57 -0700
+To: Brian Erdelyi <brian.erdelyi@gmail.com>
+X-Spam-Score: 0.0 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+X-Headers-End: 1YILwo-0000sS-Hl
+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:42:11 -0000
+
+In sending the first-signed transaction to another for second signature, how=
+ does the first signer authenticate to the second without compromising the i=
+ndependence of the two factors?
+
+Sent from my iPhone
+
+> On Feb 2, 2015, at 10:40 AM, Brian Erdelyi <brian.erdelyi@gmail.com> wrote=
+:
+>=20
+> Another concept...
+>=20
+> 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 trans=
+action that has been signed by 2 of those keys. One key is placed in cold s=
+torage and anther sent to a third-party.
+>=20
+> It is now possible to generate and sign transactions on the users computer=
+ and send this signed transaction to the third-party for the second signatur=
+e. This now permits the use of out of band transaction verification techniq=
+ues before the third party signs the transaction and sends to the blockchain=
+.
+>=20
+> If the third-party is malicious or becomes compromised they would not have=
+ the ability to complete transactions as they only have one private key. If=
+ the third-party disappeared, the user could use the key in cold storage to s=
+ign transactions and send funds to a new wallet.
+>=20
+> Thoughts?
+> --------------------------------------------------------------------------=
+----
+> Dive into the World of Parallel Programming. The Go Parallel Website,
+> sponsored by Intel and developed in partnership with Slashdot Media, is yo=
+ur
+> hub for all things parallel software development, from weekly thought
+> leadership blogs to news, videos, case studies, tutorials and more. Take a=
+
+> look and join the conversation now. http://goparallel.sourceforge.net/
+> _______________________________________________
+> Bitcoin-development mailing list
+> Bitcoin-development@lists.sourceforge.net
+> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
+
+