News for hackers. Stuff that matters.
Re:Future of Firefox DevTools by nsmartt on Monday March 18, 2013 @11:32AM (#5394780)
He had to click accept connection before it allowed him to edit the CSS.
Re:Future of Firefox DevTools by purephase on Monday March 18, 2013 @12:02PM (#5394981)
Which, as we know, is a rock-solid protection mechanism against these types of exploits. Everyone reads modal messages.
Re:Future of Firefox DevTools by past on Wednesday March 20, 2013 @06:01AM (#5406345)
In order to get to that modal message, you first have to go and enable remote debugging, which is not something normal people would do. And in general, even though we can (and already have) come up with even more mitigations for the potential threat, the sad truth is that security and usability are fundamentally a tradeoff, so you have to strike a balance at some point.
Re:Future of Firefox DevTools by purephase on Thursday March 21, 2013 @05:04PM (#5418986)
And, I understand that. But, the drawbacks of the security implications of your development/developer browsers being thus weakened is, IMO, a decision heavily weighted in favour _against_ this feature.

Personally, I would love it. It would make my life easier to have a full IDE within a browser. However, I would never be comfortable with the security tradeoff and would never enable it.

Re:Future of Firefox DevTools by Bockit on Monday March 18, 2013 @07:25PM (#5397833)
Maybe turning on some kind of dev mode to enable the feature, and then keep the modals as well.
Re:Future of Firefox DevTools by nsmartt on Monday March 18, 2013 @01:03PM (#5395479)
Fair enough. +1