canmove, Confirmed users
737
edits
Jetpack/Weekly Meeting/2012-07-31: Difference between revisions
Jump to navigation
Jump to search
→Use of resource:// URIs can leak information
| Line 61: | Line 61: | ||
==== Use of resource:// URIs can leak information ==== | ==== Use of resource:// URIs can leak information ==== | ||
Jorge: attended Blackhat. There was a session on browser privacy & fingerprinting. Web content can identify which add-ons are installed by trying to load content from at resource:// urls. For XUL add-ons, we're planning on asking developers to use chrome:// urls not resource:// urls, but SDK add-ons | Jorge: attended Blackhat. There was a session on browser privacy & fingerprinting. Web content can identify which add-ons are installed by trying to load content from at resource:// urls. For XUL add-ons, we're planning on asking developers to use chrome:// urls not resource:// urls, but SDK add-ons don't have this option. Irakli: we've talked before about having an addon:// protocol for this stuff. | ||
Alex raised a bug to track this: {{bug|779197}}. | Alex raised a bug to track this: {{bug|779197}}. | ||
=== Roundtable === | === Roundtable === | ||