Re:New clickjacking attacks expose your Gmail messages & Fac...
by chime on Thursday July 07, 2011 @11:52PM
(#2741233)
The Google OAuth attack is pretty sneaky indeed. I noticed the popup being created, positioned, and hidden upon the first click but I highly doubt most regular users would. I wish there was an option in Chrome to force new tabs to be opened instead of new windows and to completely disable popups for all sites, always. I can't think of any reason why a site needs popup anymore, especially since IFrames, OAuth, LightBox, JSONP etc. can handle pretty much all the rich-media use cases.
Re:New clickjacking attacks expose your Gmail messages & Fac...
by mvzink on Friday July 08, 2011 @12:14AM
(#2741272)
This reminds me of one of my favorite features of Stainless (http://www.stainlessapp.com/): You could have one tab with a session in which you are only logged into Google, and use that tab only on Google websites, with a bookmark to access that session in a new tab. Then you would not be logged into Google in any other tabs.
I would really like to see development of Stainless continued, or for some of its security features to be adopted by Google Chrome. If anyone knows of such functionality, I'd like to hear about it.
Also check out the Ghostery extension (http://d.pr/DzJt); it blocks some of these sorts of elements (it doesn't, for example, block the Twitter follow button, and I don't know whether it blocks Google's OAuth)
Re:New clickjacking attacks expose your Gmail messages & Fac...
by leoh on Friday July 08, 2011 @11:45PM
(#2744954)
This has to do with the way that the way the algorithm works. When you click like, you like a page. Then, a server-side script on webperflab's server contacts Facebook's opengraph, gets a list of users, looks up information on the last user that liked the page, makes that user "unlike" the page (the page can do that, it's like kicking a user out of a group), and then returns information about that user. If, for example, another user likes the page before the script can return information about you, it will return information about the other user. The demo could probably fix this issue by having multiple groups.
Re:New clickjacking attacks expose your Gmail messages & Fac...
by yuhong on Thursday July 07, 2011 @11:53PM
(#2741236)
Ideally the deanonymization attacks would not mean much if it was just that, but that is another mess altogether. Of course, the Google OAuth attack is much more serious.
Re:New clickjacking attacks expose your Gmail messages & Fac...
by icebraining on Friday July 08, 2011 @09:17AM
(#2742279)
Personally, I just have a personal Google account without any personal data (well, except for Reader subscriptions, but that's not really important) for normal browsing in Firefox, and a Google Apps account that I use in Chrome just for contacts/calendar/email.
Now with Google+, keeping that separation would be more difficult if I wanted to use it, though, since I'd lose the integration between normal browsing and G+.
Re:New clickjacking attacks expose your Gmail messages & Fac...
by Sephr on Friday July 08, 2011 @04:06AM
(#2741651)
The OAuth attack can be solved the way Firefox solved the double-click attack for installing plugins and add-ons: temporarily disabling the positive button for 2-3 seconds, though in this case it should be disabled indefinitely until there is mouse focus over the button and only then the delay to enable the button should initiate.
Well, no, actually it just showed the instructions - NoScript is awesome - but after I enabled scripts, it opened the tab.
I would really like to see development of Stainless continued, or for some of its security features to be adopted by Google Chrome. If anyone knows of such functionality, I'd like to hear about it.
Also check out the Ghostery extension (http://d.pr/DzJt); it blocks some of these sorts of elements (it doesn't, for example, block the Twitter follow button, and I don't know whether it blocks Google's OAuth)
Now with Google+, keeping that separation would be more difficult if I wanted to use it, though, since I'd lose the integration between normal browsing and G+.