jdale wrote: litedesign wrote: jdale wrote: Quote: The malware, which masqueraded as a legitimate cryptocurrency app, worked by replacing wallet addresses copied into the Android clipboard with one belonging to attackers



Looking beyond this particular app, I wonder if the concept of the clipboard needs a rethink. Essentially, the clipboard is short term memory that can be used for moving and duplicating data both within and between different apps. I think that's fairly universal between operating systems. It's extremely convenient and a frequent need, but because the data transitions through a space accessible to all apps, it's inherently insecure.



Is there a reason an app operating in the background should be able to see data on the clipboard?



If an app is operating in the foreground, would it be possible for the OS to control pasting so the app can't see the data until the user decides to paste it?



Could an app specify when the data is copied that it should be accessible only to that app, or only to an intended recipient app? Looking beyond this particular app, I wonder if the concept of the clipboard needs a rethink. Essentially, the clipboard is short term memory that can be used for moving and duplicating data both within and between different apps. I think that's fairly universal between operating systems. It's extremely convenient and a frequent need, but because the data transitions through a space accessible to all apps, it's inherently insecure.Is there a reason an app operating in the background should be able to see data on the clipboard?If an app is operating in the foreground, would it be possible for the OS to control pasting so the app can't see the data until the user decides to paste it?Could an app specify when the data is copied that it should be accessible only to that app, or only to an intended recipient app?



Why should any app have access to the clipboard, without the user giving a “Paste” command? Why should any app have access to the clipboard, without the user giving a “Paste” command?



I assume the answer to that would be "so the app can define its own UI for the Paste action." And because security has always been an afterthought, I'm sure no one ever thought about that.



But requiring that the user interact with the operating system's UI for pasting would be more secure, and these days we need to prioritize that. I assume the answer to that would be "so the app can define its own UI for the Paste action." And because security has always been an afterthought, I'm sure no one ever thought about that.But requiring that the user interact with the operating system's UI for pasting would be more secure, and these days we need to prioritize that.



Well, also, because the entire purpose of the clipboard is to copy from one application to the other.

Blocking applications from the clipboard would make it somewhat pointless. There would be literally no use for it.



You could argue that permission should be given on an app-by-app basis, but that is pretty extreme for a very very very VERY minor problem.

There are security issues a thousand time worse than clipboard access that Google needs to address first. Well, also, because theof the clipboard is to copy from one application to the other.Blocking applications from the clipboard would make it somewhat pointless. There would be literally no use for it.You could argue that permission should be given on an app-by-app basis, but that is pretty extreme for a very very very VERY minor problem.There are security issues a thousand time worse than clipboard access that Google needs to address first.