News for hackers. Stuff that matters.
Re:Show HN: PixelBlock – A Gmail extension that blocks email... by thrownaway2424 on Wednesday June 11, 2014 @03:47PM (#7880043)
I really really really want a better security model for chrome extensions. As an example, I'd be happy to install this extension if it didn't "have access to" my gmail content, but was somehow able to add DOM matching and mutating callbacks that were run under Gmail. The matching part would be under my control and couldn't be updated by the extension. For example I'd be happy to let this extension mutate any img tag. I'm sure you can find a million holes in this idea, but it would be better than what we have today.
Re:Show HN: PixelBlock – A Gmail extension that blocks email... by alooPotato on Wednesday June 11, 2014 @04:18PM (#7880195)
Maybe if the permission was something like "Let this extension read and mutate stuff on the page but don't let it make any ajax requests". Would that be sufficient?
Re:Show HN: PixelBlock – A Gmail extension that blocks email... by joshuacc on Wednesday June 11, 2014 @04:33PM (#7880272)
Not the person you were responding to, but this could be easily worked around by sticking `img` tags into the page with urls that are crafted to share information.