public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeffrey Paul <jp@eeqj•com>
To: Andreas Schildbach <andreas@schildbach•de>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal - Address Paste Improvement
Date: Thu, 8 Nov 2018 09:12:17 -0800	[thread overview]
Message-ID: <87B5B4C0-380C-4DFC-85D0-D40D941F212C@eeqj.com> (raw)
In-Reply-To: <prvlaj$8er$1@blaine.gmane.org>



> On Nov 7, 2018, at 13:28, Andreas Schildbach via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> Copying addresses to the clipboard should be discouraged, rather than
> supported.
> 
> It is an inherently insecure mechanism. Regardless of the OS used, any
> application can monitor the clipboard for Bitcoin addresses and replace
> any address with their own, usually without any specific permission or
> confirmation by the user. Effectively this steals Bitcoins if the user
> doesn't compare addresses manually.
> 
> This is a real risk, as this kind of malware has already been seen.

One can also make the argument that if the user's clipboard is able to be read/modified, then their working environment is already compromised and that the responsibility is already not upon specific application software, but the user or OS.

Down here in the real world, an application that does not support copying and pasting of addresses is not an application that is very useful (to say the least) to many people who want to manage their own wallet, though I understand your desire to avoid such.  Perhaps offering alternatives such as supporting signed BIP70 payment requests is what you mean to do.

That said, I still think working around specific malware threats and vectors isn't the application's job, especially when doing so for a tiny, tiny fraction of users that have malware outweighs the needs of the 95%+ that need to support the "I have an address on my clipboard I need to pay" case.

Best,
-jp

-- 
Jeffrey Paul
+1 312 361 0355
+49 176 8058 2122 (signal)

      parent reply	other threads:[~2018-11-08 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 14:09 Adam Ficsor
2018-11-07 21:28 ` Andreas Schildbach
2018-11-08  8:11   ` Dmitry Petukhov
2018-11-08 15:28     ` Andreas Schildbach
2018-11-08 18:00       ` Dmitry Petukhov
2018-11-12  3:23         ` Adam Ficsor
2018-12-01  4:57           ` James MacWhyte
2018-12-01 12:07             ` Adam Ficsor
2018-11-08 17:43     ` Moral Agent
2018-11-08 17:12   ` Jeffrey Paul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87B5B4C0-380C-4DFC-85D0-D40D941F212C@eeqj.com \
    --to=jp@eeqj$(echo .)com \
    --cc=andreas@schildbach$(echo .)de \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox