Jetpack/Weekly Meeting/2012-07-31: Difference between revisions

Jump to navigation Jump to search
Line 47: Line 47:


=== SDK ===
=== SDK ===
==== SDK repack ====
Alex repacked all repackable add-ons that are hosted on AMO. He doesn't have the privileges to upload them back the AMO's FTP site, so needs Jeff to do that.
The plan is to email each developer with a link to their repacked add-on, asking them to test it, and, if it looks good, to update their add-on on AMO. So add-on developers remain in control of the process.
What if add-on developers don't respond? We hope that if there are problems, people will tell us.
Irakli: will the repack include the [https://github.com/mozilla/addon-sdk/commit/cf278faecfe9d129f78907d51e11d5051432cdb4 change for Components]? Alex: no, and it's not directly related, since that change is for low-level API users, and we're not repacking low-level API users.
Alex [https://github.com/ochameau/jetpack-repacker/tree/master/scripts repacker scripts documented the repacking scripts and process]. He's on PTO for 2 weeks from next week.
==== 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 can't. Irakli: we've talked before about having an addon:// protocol for this stuff.
Alex raised a bug to track this: {{bug|779197}}.


=== Roundtable ===
=== Roundtable ===
canmove, Confirmed users
737

edits

Navigation menu