Using a desktop website and mobile device for 2/3 multisig in lieu of a
hardware device (trezor) and desktop website (mytrezor) works, but the key
is that the device used to input the two signatures cannot be in the same
band. What you are protecting against are MITM attacks. The issue is
-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin
malware
Using a desktop website and mobile device for 2/3 multisig in lieu of a
hardware device (trezor) and desktop website (mytrezor) works, but the key is
that the device used to input
TREZOR like devices with BIP70 support and third party cosigning services
are a solution I really like the sound of. I suppose though that adding
BIP70 request signature validation and adding certificate revocation
support starts to balloon the scope of what is supposed to be a very simple
Regardless, I think a standard for passing partially signed transactions
around might make sense (maybe a future extension to BIP70), with attention
to both PC - small hardware devices and pushing stuff around on the
Internet. It would be great if users had a choice of hardware signing
:38:07%20MST
From: Eric Voskuil e...@voskuil.org mailto:e...@voskuil.org
Subject: Re: [Bitcoin-development] Proposal to address Bitcoin malware
To: Brian Erdelyi brian.erde...@gmail.com
mailto:brian.erde...@gmail.com
Cc: Bitcoin Dev bitcoin-development@lists.sourceforge.net
mailto:bitcoin
5 matches
Mail list logo
