Google has announced a redesign in the upcoming Chrome 97 release for managing browser-stored data. In the section 'Settings > Privacy and Security > Site Settings > View permissions and data stored across files', a new interface 'chrome://settings/content/all' will be applied by default. The most noticeable difference in the new interface is the focus on permission settings and the removal of all site cookies at once, without the option to view detailed information about individual cookies or selectively delete them.
According to Google, allowing access to manage individual cookies for an average user, who may not understand the nuances of web development, can lead to unpredictable site malfunctions due to careless changes in specific parameters, as well as accidental disabling of privacy protection mechanisms activated through cookies. For those needing to manipulate specific cookies, it is recommended to use the storage management section in the web developer tools (Application/Storage/Cookie), which is intended for professional web developers, yet it isn’t as clear and understandable for regular users as the old interface 'chrome://settings/siteData'.
Additionally, there is a noted issue with users publishing their browser profiles on GitHub. One security researcher pointed out that there are about 4,000 repositories on GitHub containing the binary file cookies.sqlite, which holds a database of cookies from Firefox (similar files for Chrome can also be found on GitHub, but the study focuses on Firefox). This cookie database file also contains session IDs that allow access to a user's account on various sites. The reasons for users publishing their browser profiles on GitHub are not entirely clear; perhaps they are using GitHub as a platform to transfer basic settings.
Source: opennet.ru
