- Can we make sure 1.8.2 is up there this week? bug 777432
- repack: addons repacked with 1.8.2, needs to send mails now.
- repacker scripts Scripts and documentation on how to execute an AMO mass repack
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Should be updated with SDK 1.8.2 this week: bug 777432.
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 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 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 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.