Don't warn about unsigned extension installed via Debian packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Debian) |
Fix Released
|
Unknown
|
|||
firefox (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
"Mozilla is in the progress of requiring extensions to be signed, which I think is a good thing. However, for Debian packages we
already have it signed by the Developer uploading it, I see no need to have Mozilla also sign it. I suggest we don't warn / disable about extensions installed on the system, but do require the signature for those that are installed by browser itself." [1]
Shipping signed extensions in Debian packages is no options, because then we could only ship unmodified, pre-build extensions. That contradicts the Debian Free Software Guidelines (DFSG) #3 and signed extensions are not the preferred source for modification.
So, please allow unsigned extensions installed in the system directory. Debian already applied a patch for it (see Debian bug #800150). Everyone having write access to the system directory would probably also have access to the files of Firefox and could tinker with it.
This severity of this bug will raise when Mozilla will reject unsigned extensions (planned for Firefox 44).
Changed in firefox (Ubuntu): | |
importance: | Undecided → High |
Changed in iceweasel (Debian): | |
status: | Unknown → Fix Released |
tags: | added: patch |
This isn't something that we're going to be changing in Ubuntu