Android Security Auditing: Investigating Unauthorized Screenshots

Re:Android Security Auditing: Investigating Unauthorized Scr... by saagarjha on Saturday November 10, 2018 @05:11AM (#18420700)

> Your conversations aren't nearly as sensitive to require such a large breach of usability.

Yours might not be, but this isn’t true for everyone.

[ Parent | on HN ]

Re:Android Security Auditing: Investigating Unauthorized Scr... by oliwarner on Saturday November 10, 2018 @06:15AM (#18420863)

I think the broader point is that it stops the user doing something they want to. Something they could still do with a camera.

The flag should secure it from other apps but the user screenshot tool should be able to override it. The cap framework should be able to do this, you just need to insulate the app itself to ensure only real people can use it.

[ Parent | on HN ]

Re:Android Security Auditing: Investigating Unauthorized Scr... by izacus on Saturday November 10, 2018 @06:12AM (#18420852)

I'd be happy to hear about an attack vector that compromises encrypted private OS storage on Android, but does not compromise the apps view hierarchy rendered by the same OS. FLAG_SECURE is just an OS flag though.

Because your sentence just sounds like platitude without any thought behind it.

[ Parent | on HN ]