Re:How does Facebook disable Developer Tools?
by tokenizerrr on Wednesday February 12, 2014 @07:56AM
(#7223978)
Web browsers had had the capability to execute javascript through the URL bar since as long as I can remember. Social engineers should be able to just bypass this by telling users to copy paste the following code, Control+L, type "javascript:" (chrome strips it when copy-pasting), Control+V, Enter.
If people can be tricked into executing code in the dev console, then why not this too?
[ Parent
| on HN ]
Re:How does Facebook disable Developer Tools?
by dorward on Wednesday February 12, 2014 @08:12AM
(#7224027)
Browsers have already started to remove/limit code execution capability from the address bar.
Re:How does Facebook disable Developer Tools?
by EGreg on Wednesday February 12, 2014 @01:04PM
(#7226039)
Wait does this mean bookmarklets will fail in those browsers from now on?
Re:How does Facebook disable Developer Tools?
by shdon on Wednesday February 12, 2014 @01:11PM
(#7226090)
My bookmarklets run just fine, JS in the URL-bar doesn't.
Re:How does Facebook disable Developer Tools?
by Bwoup on Friday February 14, 2014 @04:36PM
(#7241134)
But bookmarklets execute via the URL bar, that's all they are...
Re:How does Facebook disable Developer Tools?
by EGreg on Thursday February 13, 2014 @12:41AM
(#7229697)
Do the bookmarklets execute in the context of the page?
Re:How does Facebook disable Developer Tools?
by shdon on Thursday February 13, 2014 @05:10AM
(#7230535)
Yes, they work just as they've always done.
Re:How does Facebook disable Developer Tools?
by Ellipsis753 on Wednesday February 12, 2014 @08:16AM
(#7224045)
That no longer works in newer Firefox (and I think Chrome?).
You can turn that back on in about::settings though.
edit: Ooops, someone had already made a post to this effect. Sorry.
Re:How does Facebook disable Developer Tools?
by tokenizerrr on Wednesday February 12, 2014 @11:29AM
(#7225213)
I tested it in Chrome before posting. Notably it removes the javascript: from the clipboard, but that's why I said to have the user type that part.