Bug 1257566 - Create firefox-unbranded package to prevent loss of functionality due to addon signing
Summary: Create firefox-unbranded package to prevent loss of functionality due to addo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-27 11:09 UTC by Richard Z.
Modified: 2015-08-28 08:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-28 08:41:28 UTC


Attachments (Terms of Use)

Description Richard Z. 2015-08-27 11:09:36 UTC
With Firefox 42 and later it will no longer be possible to install addons not signed by mozilla
  https://wiki.mozilla.org/Addons/Extension_Signing

Firefox 42 may arrive in November 2015 ( https://wiki.mozilla.org/RapidRelease/Calendar )

This will affect both Fedora specific addons and private addons maintained by single users or some companies for the private/internal use. The only currently known ways to avoid loss of functionality is to have a developer or "unbranded" version.

Given the November date there may not be much time to loose.

Comment 1 Martin Stransky 2015-08-27 12:44:50 UTC
Yes, so don't waste time and submit your unbranded package for review. See https://fedoraproject.org/wiki/Package_Review_Process for details. You can use pretty much the recent firefox package as a template, you just need to change name and remove the branding stuff.

Comment 2 Martin Stransky 2015-08-28 08:41:28 UTC
Actually there's an unbranded Firefox package - https://apps.fedoraproject.org/packages/icecat - so you don't need to create anything and just use this one.

Anyway, new packages have to still keep processes for new packages so for any new package submission please follow the Fedora review process.


Note You need to log in before you can comment on or make changes to this bug.