📅 Original date posted:2015-02-02
📝 Original message:Joel,
The mobile device should show you the details of the transaction (i.e. amount and bitcoin address). Once you verify this is the intended recipient and amount you approve it on the mobile device. If the address was replaced, you should see this on the mobile device as it won’t match where you were intending to send it. You can then not provide the second signature.
Brian Erdelyi
> On Feb 2, 2015, at 4:57 PM, Joel Joonatan Kaartinen <joel.kaartinen at gmail.com> wrote:
>
> If the attacker has your desktop computer but not the mobile that's acting as an independent second factor, how are you then supposed to be able to tell you're not signing the correct transaction on the mobile? If the address was replaced with the attacker's address, it'll look like everything is ok.
>
> - Joel
>
> On Mon, Feb 2, 2015 at 9:58 PM, Brian Erdelyi <brian.erdelyi at gmail.com <mailto:brian.erdelyi at gmail.com>> wrote:
>
> > Confusing or not, the reliance on multiple signatures as offering greater security than single relies on the independence of multiple secrets. If the secrets cannot be shown to retain independence in the envisioned threat scenario (e.g. a user's compromised operating system) then the benefit reduces to making the exploit more difficult to write, which, once written, reduces to no benefit. Yet the user still suffers the reduced utility arising from greater complexity, while being led to believe in a false promise.
>
> Just trying to make sure I understand what you’re saying. Are you eluding to that if two of the three private keys get compromised there is no gain in security? Although the likelihood of this occurring is lower, it is possible.
>
> As more malware targets bitcoins I think the utility is evident. Given how final Bitcoin transactions are, I think it’s worth trying to find methods to help verify those transactions (if a user deems it to be high-risk enough) before the transaction is completed. The balance is trying to devise something that users do not find too burdensome.
>
> Brian Erdelyi
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> 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/ <http://goparallel.sourceforge.net/>;
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net <mailto:Bitcoin-development at lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>;
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150202/ed32b523/attachment.html>;
Brian Erdelyi [ARCHIVE] /
npub1ta…j25sq
2023-06-07 15:29:18
in reply to nevent1q…gzg2
Author Public Key
npub1tatcq4sq4leywpxwgqd90eut5933h62lrrnzu28mx95w80s75hzspj25sqSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:29:18Event JSON
{
"id": "9c0fe23eb1e0399962d1774715bccfeb68722e06f444b040d4d17c9669828c7d",
"pubkey": "5f57805600aff24704ce401a57e78ba1631be95f18e62e28fb3168e3be1ea5c5",
"created_at": 1686151758,
"kind": 1,
"tags": [
[
"e",
"541657d412739d9d2a5bc263564b0f2ef650e16ac828484a06cbef551e18c76c",
"",
"root"
],
[
"e",
"13bdc1b5434724ff4dea0a7816e43e36cc13bde02f7d7bf13b946c0fb7c59cc3",
"",
"reply"
],
[
"p",
"d52a1b72551bba47beb14639a1b6f5e6cd98603ecbaaa6ab02031708d9cc4473"
]
],
"content": "📅 Original date posted:2015-02-02\n📝 Original message:Joel,\n\nThe mobile device should show you the details of the transaction (i.e. amount and bitcoin address). Once you verify this is the intended recipient and amount you approve it on the mobile device. If the address was replaced, you should see this on the mobile device as it won’t match where you were intending to send it. You can then not provide the second signature.\n\nBrian Erdelyi\n\n\u003e On Feb 2, 2015, at 4:57 PM, Joel Joonatan Kaartinen \u003cjoel.kaartinen at gmail.com\u003e wrote:\n\u003e \n\u003e If the attacker has your desktop computer but not the mobile that's acting as an independent second factor, how are you then supposed to be able to tell you're not signing the correct transaction on the mobile? If the address was replaced with the attacker's address, it'll look like everything is ok.\n\u003e \n\u003e - Joel\n\u003e \n\u003e On Mon, Feb 2, 2015 at 9:58 PM, Brian Erdelyi \u003cbrian.erdelyi at gmail.com \u003cmailto:brian.erdelyi at gmail.com\u003e\u003e wrote:\n\u003e \n\u003e \u003e Confusing or not, the reliance on multiple signatures as offering greater security than single relies on the independence of multiple secrets. If the secrets cannot be shown to retain independence in the envisioned threat scenario (e.g. a user's compromised operating system) then the benefit reduces to making the exploit more difficult to write, which, once written, reduces to no benefit. Yet the user still suffers the reduced utility arising from greater complexity, while being led to believe in a false promise.\n\u003e \n\u003e Just trying to make sure I understand what you’re saying. Are you eluding to that if two of the three private keys get compromised there is no gain in security? Although the likelihood of this occurring is lower, it is possible.\n\u003e \n\u003e As more malware targets bitcoins I think the utility is evident. Given how final Bitcoin transactions are, I think it’s worth trying to find methods to help verify those transactions (if a user deems it to be high-risk enough) before the transaction is completed. The balance is trying to devise something that users do not find too burdensome.\n\u003e \n\u003e Brian Erdelyi\n\u003e ------------------------------------------------------------------------------\n\u003e Dive into the World of Parallel Programming. The Go Parallel Website,\n\u003e sponsored by Intel and developed in partnership with Slashdot Media, is your\n\u003e hub for all things parallel software development, from weekly thought\n\u003e leadership blogs to news, videos, case studies, tutorials and more. Take a\n\u003e look and join the conversation now. http://goparallel.sourceforge.net/ \u003chttp://goparallel.sourceforge.net/\u003e\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development \u003chttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\u003e\n\u003e \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150202/ed32b523/attachment.html\u003e",
"sig": "04df6b562ff33ff07932c7a7f3fa5606731df89d2290295019b048ec3182e66f92e7647b851bfa5cbe3b5eaa19dd234d6210963f67fceeba736f7133386d2241"
}