On unreleased Android L preview2 there are STILL vulnerabilities in what is shown on an interface and what a user taps. So, be warned that the future of ambiguous tapping and running unintended functionality is still in everyone's future unless Android team patches them prior to release...
-- Regards, Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen On Sep 11, 2014 4:48 PM, "James Hudon" <[email protected]> wrote: > Apparently you can protect against tapjacking with an attribute > filterTouchesWhenObscured ( > https://blog.lookout.com/blog/2010/12/09/android-touch-event-hijacking/). > However, apparently since Android 4.0.3, this is not necessary ( > http://commonsware.com/blog/2012/03/03/tapjacking-defunct.html). > > Can anyone confirm what is being said in the latter source? Is the > filterTouchesWhenObscured > attribute actually not needed anymore? > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Android Security Discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to > [email protected]. > Visit this group at > http://groups.google.com/group/android-security-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-security-discuss. For more options, visit https://groups.google.com/d/optout.
