Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Security Auditing: Investigating Unauthorized Screenshots

tech.michaelaltfield.net

Post reply on HN
Print view View original

41–43 of 43 posts

Re: Android Security Auditing: Investigating Unauthorized Screenshots

#41

Post by rhamzeh »

solarkraft wrote: post #27
RafiqM wrote: post #6

Earlier quoted context omitted.

The conclusion is there's no problem, that it wasn't the nefarious activity that he originally thought it was. The additional point he's trying to make is that app developers should use FLAG_SECURE if its confidential data - messaging probably should be, and his bitcoin app should almost certainly be.

I hate apps using FLAG_SECURE with full passion. I want to take a fucking screenshot and you don't allow me to.

I know some password managers (myki, lastpass and I think 1Password have an option to toggle it off).

It's on by default, which should be true for most apps with confidential data. But other apps (like photos and messaging apps, can at least have that as an option defaulted to false, for users who would like the extra privacy)

Re: Android Security Auditing: Investigating Unauthorized Screenshots

#42

Post by tjoff »

kbenson wrote: post #38
tjoff wrote: post #37

Earlier quoted context omitted.

Yeah, for some reason web browsers feel the need to do that when browsing in private mode. It is one thing to block automatic screenshots or screen recordings. Another when the user explicitly tries to take a screenshot.

I imagine the reasoning is that if you can do it, some other app might be able to trigger it, and at that point, it's all downhill.

It's an OS function triggered by a physical button. If some other app can imitate that then surely it is already game over?
Post reply on HN