Exploiting IndexedDB API information leaks in Safari 15
fingerprintjs.com
Exploiting IndexedDB API information leaks in Safari 15
1–10 of 99 posts
Re: Exploiting IndexedDB API information leaks in Safari 15
#2Re: Exploiting IndexedDB API information leaks in Safari 15
#3Re: Exploiting IndexedDB API information leaks in Safari 15
#4Wow. I wonder what Brave thinks of this?
Re: Exploiting IndexedDB API information leaks in Safari 15
#5What the web needs is fewer APIs.
Re: Exploiting IndexedDB API information leaks in Safari 15
#6> and in all browsers on iOS and iPadOS 15 Wow. I wonder what Brave thinks of this?
Re: Exploiting IndexedDB API information leaks in Safari 15
#7On the other hand they report (and help close) some gnarly exploits like this via sketchy web apis.
What do you all make of this? It's hard to not see it as some weird "were not doing a bad thing" gaslighting (perhaps even internally to their team).
Re: Exploiting IndexedDB API information leaks in Safari 15
#8Re: Exploiting IndexedDB API information leaks in Safari 15
#9What the web needs is fewer APIs.
What we need are companies working on browsers that actually care about the web. Apple have demonstrated time and time again that they don't, because they favor native applications on iOS and macOS over anything web, so we end up with subpar browsers who ship with the OSes. In some cases (iOS), we even end up with a browser-monopoly where no other browser is even welcome.
Re: Exploiting IndexedDB API information leaks in Safari 15
#10> and in all browsers on iOS and iPadOS 15 Wow. I wonder what Brave thinks of this?
All browser vendors are very unhappy that Apple only allows their browser engine on iOS. For security and many other reasons.