News for hackers. Stuff that matters.

A comment on Multisig Vault. Parent comment

Re:Multisig Vault by jerguismi on Wednesday October 29, 2014 @02:59PM (#8529140)
Which makes me wonder... The keys are generated in-browser. What if the users computer is compromised, and a malware succeeds in capturing the keys + bip38 passphrase? I don't know if this product will be pain in the ass for coinbase, if the user funds start disappearing from these multisig addresses.

All the best luck for this product, though.

[ Parent | on HN ]
Re:Multisig Vault by adrianmacneil on Wednesday October 29, 2014 @03:10PM (#8529218)
If the computer is infected, then yes it would be possible to steal both the private keys, and the passphrase. To avoid this attack scenario, we're investing pretty heavily in technologies such as CSP.

However, this can be mitigated with our group multisig vault, where separate users create their own keys. For malware to steal these, it would require infecting multiple computers.

[ Parent | on HN ]
Re:Multisig Vault by icebraining on Wednesday October 29, 2014 @06:31PM (#8530379)
Seems like the next step would be to allow the users to store their copies on a smart card instead of a PC.
[ Parent | on HN ]
Re:Multisig Vault by wcoenen on Thursday October 30, 2014 @04:12AM (#8531877)
Like the Trezor[1] hardware wallet.

[1] http://www.bitcointrezor.com

[ Parent | on HN ]
Re:Multisig Vault by icebraining on Thursday October 30, 2014 @04:26AM (#8531900)
Yes, but maintaining the encrypted copy on Coinbase's servers, to ensure that losing the card doesn't mean losing the wallet.
[ Parent | on HN ]
Re:Multisig Vault by wcummings on Wednesday October 29, 2014 @06:42PM (#8530421)
CSP?
[ Parent | on HN ]
Re:Multisig Vault by floatrock on Wednesday October 29, 2014 @06:58PM (#8530467)
Content Security Policy -- http://en.wikipedia.org/wiki/Content_Security_Policy

basically headers that can tell the browser not to execute stuff that leads to injection like inline javascript or inline styling, allows for whitelists of domains (so the browser won't run script src="http://hackercdn.com/malicious.js"), etc.

[ Parent | on HN ]