Re:It is not possible to detect and block Chrome headless
by gildas on Thursday January 18, 2018 @01:23PM
(#16179775)
The problem is that you can easily detect that some properties have been overloaded. For example, you can execute Object.getOwnPropertyDescriptor(navigator, "languages") to detect if navigator.languages is a native property or not.
[ Parent
| on HN ]
Re:It is not possible to detect and block Chrome headless
by sigotirandolas on Thursday January 18, 2018 @01:47PM
(#16180041)
It's possible to hide that as well, funnily enough, by also overwriting Object.getOwnPropertyDescriptor (and similar tricks). As far as I know, it's theoretically possible to use this trick to completely 'sandbox' some code so that there's no way it can detect certain functions being overwritten (by overwriting all functions such as Object.getOwnPropertyDescriptor, Function.toString, etc. and making them hide the overwritten functions, including themselves).
For some more information: http://randomwalker.info/publications/ad-blocking-framework-...
Re:It is not possible to detect and block Chrome headless
by gildas on Thursday January 18, 2018 @01:51PM
(#16180077)
Very interesting article! Thank you.
Re:It is not possible to detect and block Chrome headless
by numbsafari on Thursday January 18, 2018 @01:27PM
(#16179812)
Can’t I accomplish the same thing by compiling a modified version of headless chrome?