Firefox to enter same Signed Extension dead end as MaxThon it seems

[MilesAhead]

Hmm, I hope it doesn't go the way of MaxThon with only the few writing extensions:

https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/

 

[Anak]

From what I read on the blog link there will be wailing and gnashing of teeth by the masses.

 

[MilesAhead]

From what I read on the blog link there will be wailing and gnashing of teeth by the masses.

It seems like a suicidal move to me. I tried MaxThon 3 awhile back for nostalgic reasons, not knowing what had happened with the extension signing there. I couldn't even find the communities where I used to hang out and ask questions about user written extensions. It was really sad to see.

 

[Anak]

Well, we better have our helmets an flack-jackets ready when the deluge starts. I'm thinking I better check my add-ons and extensions for signage to see if they'll pass or not, only 3more versions to go if they do start the warnings with v39.

It'd be nice if mozilla had a tool to verify signage, but the only one I can find is this: https://mozilla Check Your Plugins | www.mozilla.org and I don't think it does.

 

[MilesAhead]

Official notification extension signing will be enforced with the release of FF 41 due on Sept. 22

https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/

 

[MoxieMomma]

AFAIK Currently, the plan is:
Firefox 40: Firefox warns about signatures but doesn't enforce them.
Firefox 41: Firefox will have a preference that allows signature enforcement to be disabled (xpinstall.signatures.required in about:config).
Firefox 42: Release and Beta versions of Firefox 42.0 will not allow unsigned extensions to be installed, with no override

I can't put my finger on the link at this moment, but I had seen discussion of this at forums.mozillazine.org and mention that ths was going to be pushed back to the next version.
Having said that, I don't have a source to substantiate that.

So, I mention it only in conversation, and the links to the official blog would, of course, seem to be more authoritative.

Cheers,

 

[Anak]

The schedule you refer to is found in Miles Link: The Future of Developing Firefox Add-ons It is slightly different and that may be due to you seeing it (the schedule) in a blog or those mozillazine.org forums you mentioned.

Scroll down until you reach the fourth paragraph in the Signing section; This was current as of two days ago (08/21/15):

The full schedule for add-on signing is currently as follows:

• Firefox 40: Users will see a warning in the add-ons manager about unsigned extensions, but all extensions will continue to work.
• Firefox 41: Unsigned extensions will be disabled by default, and Firefox will have a preference (xpinstall.signatures.required) that allows signature enforcement to be turned off.
• Firefox 42 and beyond:
  • The Beta and Release versions of Firefox based on 42 and above (Beta 42 will be released at the same time as Firefox 41) will remove the preference that allows unsigned extensions to be installed, and will disable and/or prevent the installation of unsigned extensions.
  • The Nightly and Developer Editions of Firefox based on 42 and above will retain the preference to disable signing enforcement, allowing the development and/or use of unsigned add-ons in those versions. Unbranded versions of Firefox based on releases will also be made available for developers, and are expected to be in place for Firefox 42 for release (and potentially beta).