Pixnapping Attack
pixnapping.com
Pixnapping Attack
1–10 of 75 posts
Re: Pixnapping Attack
#2Re: Pixnapping Attack
#3Re: Pixnapping Attack
#4Discussion: https://news.ycombinator.com/item?id=45574613
But in this write up they say the patch doesn’t work fully
Re: Pixnapping Attack
#5Discussion: https://news.ycombinator.com/item?id=45574613
In the previous discussion everyone seems happy it’s been patched and not to worry (even though androids mostly don’t run anything like the latest android) But in this write up they say the patch doesn’t work fully
While these blurs make the sidechannel easier to use as it provides a clear signal, considering you can predict the exact contents of the screen I feel like you could get away with just a mask.
Re: Pixnapping Attack
#6Re: Pixnapping Attack
#7Not a phone designer, but could we imagine a new class of screen region which is excluded from screen grab, draw over and soft focus with a mask, and then notification which do otp or pin subscribe to use it?
Re: Pixnapping Attack
#8Throw a privacy notice to the users "This app will take periodic screenshots of your phone" You'd be amazed how many people will accept it.
> Did you release the source code of Pixnapping? We will release the source code at this link once patches become available: https://github.com/TAC-UCB/pixnapping
It's not exactly impossible to reverse what's happening here. You could have waited until it was patched but sounds like you wanted to get your own attention as soon as possible.
Re: Pixnapping Attack
#9We have this tendency of adding more and more "features", more and more functionality 85% of which nobody asked for or has use for.
I believe that there will be a market for a small, bare bones secure OS in the future. Akin to how freeBSD is being run.
Re: Pixnapping Attack
#10Not a phone designer, but could we imagine a new class of screen region which is excluded from screen grab, draw over and soft focus with a mask, and then notification which do otp or pin subscribe to use it?
App developers can already dynamically mark their windows as secure which should prevent any other app from reading the pixels it rendered. The compositor composites all windows, including secure windows and applies any effects like blur. No apps are supposed to be able to see this final composited image, but this attack uses a side channel they found that allows apps on the system to learn information about the pixe…