News for hackers. Stuff that matters.
Re:Detecting Chrome headless by heipei on Saturday August 05, 2017 @11:49AM (#14936262)
There are multiple ways to hide your IP for free: Public proxies, VPNs which are not so well-known, and lastly there is a wealth of browser extensions which aim at hiding your IP to some extent. This would be one example where your traffic will exit with actual users on consumer ISP lines: http://hola.org/
Re:Detecting Chrome headless by ficklepickle on Saturday August 05, 2017 @09:01PM (#14939071)
I'd say don't use Hola. They've had some issues, like selling their users bandwidth for botnets[1].

If you do some googling, you will see many reasons not to use that extension.

[1]http://www.theverge.com/2015/5/29/8685251/hola-vpn-botnet-se...

Re:Detecting Chrome headless by ant6n on Saturday August 05, 2017 @02:01PM (#14936964)
What about tor.
Re:Detecting Chrome headless by heipei on Saturday August 05, 2017 @02:26PM (#14937110)
TOR is an easy one to detect. Case in point: Try to browse the web with TOR and see how many CloudFlare captchas you have to solve in the first 10 minutes ;)

Also TOR has public lists of exit nodes (https://torstatus.blutmagie.de/), and unless you exit via a non-listed one you're trivially identifiable.

Lastly, TOR is rather slow, which prohibits using for large-scale scraping tasks. Plus you get switched around different exits and countries, which might break your scraping logic.

Re:Detecting Chrome headless by crtasm on Sunday August 06, 2017 @01:47PM (#14942401)
I believe you could use the ExitNodes option to only use a specific exit.

There's no such thing as an unlisted exit node, only unlisted entry nodes (bridges). I agree that Tor isn't a good choice for scraping.

Re:Detecting Chrome headless by dsacco on Saturday August 05, 2017 @02:45PM (#14937221)
Tor would introduce pretty intolerable latency into a professional data crawling setup.