> At a high level, the DBSC API lets a server start a new session with a specific browser on a device. When the browser starts a new session, it creates a new public/private key pair locally on the device, and uses the operating system to safely store the private key in a way that makes it hard to export. Chrome will use facilities such as Trusted Platform Modules (TPMs) for key protection, which are becoming more commonplace and are required for Windows 11, and we are looking at supporting software-isolated solutions as well.
Seems like a cat-and-mouse game never ends, and now they want to include hardware mingling with cookies - go adtech, go!
If your user env is compromised its too late; just a matter of time before that vector gets exploited.
I dont want the same convince as other people choose to have; just force log me off of sites after a time limit, stop tracking me and give me my internet without javascript back (imagine going back to 2000 and suggesting to stop using Flash, lol)
Seems like a cat-and-mouse game never ends, and now they want to include hardware mingling with cookies - go adtech, go!
If your user env is compromised its too late; just a matter of time before that vector gets exploited.
I dont want the same convince as other people choose to have; just force log me off of sites after a time limit, stop tracking me and give me my internet without javascript back (imagine going back to 2000 and suggesting to stop using Flash, lol)