{"id":37590,"date":"2020-10-09T16:01:56","date_gmt":"2020-10-09T16:01:56","guid":{"rendered":"https:\/\/packetstormsecurity.com\/news\/view\/31650\/Chrome-Changes-How-Its-Cache-Works-To-Improve-Privacy.html"},"modified":"2020-10-09T16:01:56","modified_gmt":"2020-10-09T16:01:56","slug":"chrome-changes-how-its-cache-works-to-improve-privacy","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/chrome-changes-how-its-cache-works-to-improve-privacy\/","title":{"rendered":"Chrome Changes How Its Cache Works To Improve Privacy"},"content":{"rendered":"
\"Google<\/span>
<\/span><\/figcaption><\/figure>\n
\n

special feature<\/span> <\/h3>\n
\"Securing<\/span> <\/a> <\/div>\n

Securing Your Mobile Enterprise <\/a> <\/p>\n

Mobile devices continue their march toward becoming powerful productivity machines. But they are also major security risks if they aren’t managed properly. We look at the latest wisdom and best practices for securing the mobile workforce.<\/p>\n

Read More<\/a> <\/p>\n<\/p><\/div>\n

Google has changed how a core component of the Chrome browser works in order to add additional privacy protections for its users.<\/p>\n

Known as the HTTP Cache<\/strong> or the Shared Cache<\/strong>, this Chrome component works by saving copies of resources loaded on a web page, such as images, CSS files, and JavaScript files.<\/p>\n

The idea is that when a user revisits the same site or visits another website where the same files are used, Chrome will load them from its internal cache, rather than waste time re-downloading each file all over again.<\/p>\n

This component has been present not only inside Chrome but inside all web browsers since the early days of the internet, where it served as a bandwidth-saving feature.<\/p>\n

In all browsers, the cache system usually works in the same way. Each image, CSS, or JS file saved in the cache receive a storage key that is usually the resource’s URL.<\/p>\n

For example, the storage key for an image would be the image URL itself: https:\/\/x.example\/doge.png<\/em>.<\/p>\n

When the browser loads a new page, it would search for the key (URL) inside its internal cache database and see if it needed to download the image or load it from the cache.<\/p>\n

The old HTTP Cache system was open to abuse<\/h3>\n
<\/section>\n

Unfortunately, across the years, web advertising and analytics firms realized that this very same feature could also be abused to track users.<\/p>\n

“This mechanism has been working well from a performance perspective for a long time,” said Eiji Kitamura, Developer Advocate at Google.<\/p>\n

“However, the time a website takes to respond to HTTP requests can reveal that the browser has accessed the same resource in the past, which opens the browser to security and privacy attacks.”<\/p>\n

These include the likes of:<\/p>\n