Please allow ads on our site
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginHow does Facebook disable the browser's integrated Developer Tools?
Digital Marketing Facebook Marketing API 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Similar Forum
What are the best SEO tools for a personal website? What website or tools should I use to build and...
What are the best SEO tools for a personal website? What website or tools should I use to build and...Why is keyword research important?
Why is keyword research important?What is SEO ?
What is SEO ?Explore Other Libraries
Online Exams
Question Bank
Career News
Feeds
Full Forms
Dictionary
Interview Question
Gigs
Quotes
Lyrics
Videos
Courses
Blogs
Tutorials
Forum
Educators
Corporates
Tools
Important Digital Marketing Links
Please allow ads on our site
Kindly log in to use this feature. We’ll take you to the login page automatically.
Login
manpreet![Tuteehub forum best answer]()
Best Answer
3 years ago
_x000D_ I'm a security engineer at Facebook and this is my fault. We're testing this for some users to see if it can slow down some attacks where users are tricked into pasting (malicious) JavaScript code into the browser console. Just to be clear: trying to block hackers client-side is a bad idea in general; this is to protect against a specific social engineering attack. If you ended up in the test group and are annoyed by this, sorry. I tried to make the old opt-out page (now help page) as simple as possible while still being scary enough to stop at least some of the victims. The actual code is pretty similar to @joeldixon66's link; ours is a little more complicated for no good reason. Chrome wraps all console code in with ((console && console._commandLineAPI) || {}) {} ... so the site redefines console._commandLineAPI to throw: Object.defineProperty(console, '_commandLineAPI', { get : function() { throw 'Nooo!' } }) This is not quite enough (try it!), but that's the main trick. Epilogue: The Chrome team decided that defeating the console from user-side JS was a bug and fixed the issue, rendering this technique invalid. Afterwards, additional protection was added to protect users from self-xss.
0
views
0
shares
Facebook
Twitter
Linked In
WhatsApp