Re: Tracking with ultrasound beacons. Web Audio API privacy considerations need updating?

On Fri, Nov 13, 2015 at 10:29 AM, Joseph Lorenzo Hall <> wrote:

> In some senses, platforms can help. E.g., just like there are small
> indicators present when an app is accessing location or the microphone to
> give users notice that something is using those resources, maybe a sound
> icon could be used? Chrome I think does this with tabs so that you can
> quickly identify which of dozens of tabs is the one playing annoying audio.

Firefox does this too.

Since this attack works for native apps as well, it's probably best blocked
by filtering out inaudible frequencies at the platform level.

Also I imagine that if this gets used much in the wild, the scripts
involved will be added the blacklist used by Firefox's tracking protection.

lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr

Received on Friday, 13 November 2015 22:00:48 UTC