Proposal to address Bitcoin malware [combined summary]

• Proposal to address Bitcoin malware Eric Voskuil 2015-02-03 07:38:07+00:00
• Proposal to address Bitcoin malware Eric Voskuil 2015-02-03 00:41:20+00:00
• Proposal to address Bitcoin malware Eric Voskuil 2015-02-02 22:54:25+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 21:49:11+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 21:42:34+00:00
• Proposal to address Bitcoin malware devrandom 2015-02-02 21:30:03+00:00
• Proposal to address Bitcoin malware Pedro Worcel 2015-02-02 21:09:20+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 21:03:42+00:00
• Proposal to address Bitcoin malware Pedro Worcel 2015-02-02 21:02:13+00:00
• Proposal to address Bitcoin malware Joel Joonatan Kaartinen 2015-02-02 20:57:04+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 19:58:11+00:00
• Proposal to address Bitcoin malware Mike Hearn 2015-02-02 18:53:14+00:00
• Proposal to address Bitcoin malware Eric Voskuil 2015-02-02 18:45:49+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 18:35:59+00:00
• Proposal to address Bitcoin malware Mike Hearn 2015-02-02 18:25:14+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 18:10:12+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 18:07:52+00:00
• Proposal to address Bitcoin malware Eric Voskuil 2015-02-02 18:05:57+00:00
• Proposal to address Bitcoin malware Martin Habovštiak 2015-02-02 18:02:39+00:00
• Proposal to address Bitcoin malware Mike Hearn 2015-02-02 17:59:54+00:00
• Proposal to address Bitcoin malware Martin Habovštiak 2015-02-02 17:54:55+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-02 17:40:11+00:00
• Proposal to address Bitcoin malware mbde at bitwatch.co 2015-02-01 14:28:38+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-01 13:54:08+00:00
• Proposal to address Bitcoin malware Mike Hearn 2015-02-01 13:48:15+00:00
• Proposal to address Bitcoin malware Mike Hearn 2015-02-01 13:46:52+00:00
• Proposal to address Bitcoin malware Martin Habovštiak 2015-02-01 13:31:28+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-02-01 12:49:05+00:00
• Proposal to address Bitcoin malware Natanael 2015-01-31 23:41:54+00:00
• Proposal to address Bitcoin malware Natanael 2015-01-31 23:37:51+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-01-31 23:04:57+00:00
• Proposal to address Bitcoin malware Natanael 2015-01-31 22:38:55+00:00
• Proposal to address Bitcoin malware Brian Erdelyi 2015-01-31 22:15:53+00:00

Published on: 2015-02-03T07:38:07+00:00

Summary:

The context provided discusses the development of Bitcoin Authenticator, a desktop and mobile app aimed at addressing security concerns related to cryptocurrency transactions. The app offers out-of-band transaction verification/signing or dual transaction signing without requiring a third-party. The concept of using multisig wallets to protect against malware attacks is also discussed, where a compromised third-party would not be able to complete transactions as they only possess one private key.The conversation between Mike Hearn and Martin Habovštiak reveals that Bitcoin Authenticator was already implementing the idea of sending partially signed transactions from a computer to a smartphone. Habovštiak suggests creating a 3oo5 address with two cold storage keys on a desktop/laptop and a smartphone, along with one key using a third-party service. BitGo, CryptoCorp, and GreenAddress are mentioned as companies offering this model.The email conversation between Habovštiak and others further discusses the use of partially signed transactions from a computer to a smartphone to improve security. It suggests utilizing multisig wallets and adding more keys, including hardware wallets like Trezor and Ledger, to enhance security. The email emphasizes the importance of leaving out a third party for privacy reasons.The context highlights the increasing concern about malware targeting Bitcoin users and the need for effective security measures. Out-of-band transaction verification/signing is suggested as a method used in online banking to protect against attacks. The use of OATH-based one-time passwords (OTP) and chipTAN/cardTAN as additional security measures is also discussed.BIP70 is introduced as a safe method against Man-in-the-Browser (MitB) attacks, but questions about its sufficiency for transaction verification, especially in the case of a compromised computer, are raised. The compatibility of Trezor with BIP70 is uncertain. The security of the wallet is emphasized, and devices like TREZOR and secure wallet pairings are mentioned as examples.In a Bitcoin-development mailing list discussion, concerns about the security of Bitcoin transactions are raised. The possibility of generating an 8-digit number from a Bitcoin address to verify transactions is discussed, but there are concerns about the feasibility and potential collisions. The discussion highlights ongoing concerns about Bitcoin transaction security and the need for further development of solutions.The context also mentions the use of vanitygen for generating vanity bitcoin addresses and discusses viruses that manipulate bitcoin addresses. It suggests generating an 8-digit code for a legitimate bitcoin address as a basic mitigation measure against malware, but also acknowledges the possibility of brute-forcing the legitimate bitcoin address to generate a rogue address with the same code.Overall, the context presents various concepts and discussions related to improving the security of Bitcoin transactions, including the use of out-of-band verification, multisig wallets, hardware wallets, and additional authentication methods. The aim is to protect against malware attacks and ensure the privacy and integrity of transactions.

Updated on: 2023-08-01T11:18:34.937889+00:00