Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Eric Voskuil
On 02/03/2015 04:04 AM, Will wrote: > An idea for the bitcoin malware proposal below, the idea is at the bottom… > ... > The trick we need to look at is how to use the bitcoin network as a > delivery mechanism to bypass the need for the trusted third party in the > example above. Using the Bitcoi

Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Will
to catch on and become cost competitive. I think the key is making it invisible to the user. From: Adam Weiss Reply: Adam Weiss > Date: February 3, 2015 at 12:25:20 PM To: Will > Cc: bitcoin-development@lists.sourceforge.net > Subject:  Re: [Bitcoin-development] Subject: Re: Proposal t

Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Mike Hearn
> > 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 simp

Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Brian Erdelyi
> 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 signi

Re: [Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Adam Weiss
> > > 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 issu

[Bitcoin-development] Subject: Re: Proposal to address Bitcoin malware

2015-02-03 Thread Will
An idea for the bitcoin malware proposal below, the idea is at the bottom… 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