Re:Google has been letting app developers read users’ Gmail
by itronitron on Tuesday July 03, 2018 @12:59AM
(#17447663)
If I am giving an app explicit permission to read my email then I would expect to be asked if I give it permission to send/write/save my email. If the user isn't asked that question then why would they think the app can do that. Full disclosure >> I am a technical person.
Re:Google has been letting app developers read users’ Gmail
by ajross on Tuesday July 03, 2018 @01:37AM
(#17447815)
How do you propose to enforce such a restriction? This is the halting problem. If the app can read it, it can copy it.
Re:Google has been letting app developers read users’ Gmail
by AstralStorm on Tuesday July 03, 2018 @05:26AM
(#17448697)
Not true. There can be capabilities connected to the data stream and objects used to read emails and both platform and Play Store can reject typical invalid use. (Just like with intents giving temporary permissions.)
It would also patch some confused deputy bugs.
Make that part of API 29 or such to not break apps.
Very sneaky use can be partly detected too, but then we're talking specifically malicious apps.
Re:Google has been letting app developers read users’ Gmail
by ajross on Tuesday July 03, 2018 @10:10AM
(#17450285)
It sounds like you're trying to reinvent something like Perl's "taint" bit, but for privacy specifically? No one does that. It really didn't even work as much of a security barrier for Perl CGI scripts in 1996...
Does that really qualify as an "it turns out"? Every technical person who saw this would understand that this was an obvious capability. No one was surprised. Be serious: were you surprised?
Note also that the article points out that this kind of storage is likely a violation of the developer's contract with Google, which contains the standard privacy requirements.