Are Dates of Chrome Trust Token Files Correct or Is this a Bug?
Opened this issue · 1 comments
I am running on windows, so the directory structure here is for Chrome on WIndows 11.
If you look in the directory C:\Users\username\AppData\Local\Google\Chrome\User Data\TrustTokenKeyCommitments, there is a subdirectory with a date that holds a series of files that seem to be for Private State Tokens (the keys.json file certainly holds PST data). But note the dates on the files in the picture. They are "12/31/1979". Is this intentional and, if so, why. And if not, is this some kind of bug?
I am writing about PSTs in www.theprivacysandbox.com and want to make sure I address this correctly.
This is a bug with how components are served in Chrome and how some crx files (zipped files containing all the data) are processed. This has been a known issue with Chrome and affects other components (you can also see this happening in FirstPartySetsPreloaded for example), though I think has been relatively low priority to fix as it only affects the display date in file explorers and doesn't affect the freshness/caching of the component.