It is not possible to detect and block Chrome headless

Re:It is not possible to detect and block Chrome headless by eric_h on Thursday January 18, 2018 @02:35PM (#16180531)

> Claiming you're on windows while actually running on a Linux VM, your TCP fingerprint gives it away

This is interesting, I’d not heard of this approach. What’s the technique for generating such a fingerprint?

[ Parent | on HN ]

Re:It is not possible to detect and block Chrome headless by Savageman on Thursday January 18, 2018 @03:08PM (#16180845)

The most trivial check is using the TCP packet TTL (Time To Live). Windows and Linux doesn't have the same default value so it's "easy" to recognize which one sent a specific packet.

Just look up for "ttl windows vs linux" to find tons of article about it :)

[ Parent | on HN ]

Re:It is not possible to detect and block Chrome headless by lawl on Thursday January 18, 2018 @02:37PM (#16180550)

http://lcamtuf.coredump.cx/p0f3/

[ Parent | on HN ]

Re:It is not possible to detect and block Chrome headless by eric_h on Friday January 19, 2018 @04:18PM (#16189952)

Thanks!

[ Parent | on HN ]

Re:It is not possible to detect and block Chrome headless by mehrdadn on Thursday January 18, 2018 @02:40PM (#16180582)

I don't know the actual fingerprint here but check out nmap: https://nmap.org/

[ Parent | on HN ]