Re: (forw) [DNG] Life After Firefox 56
Deirdre Saoirse Moen <[email protected]>
| Newsgroups | gmane.org.user-groups.linux.svlug |
|---|---|
| Message-ID | <[email protected]> |
> On Nightly and Developer Edition builds, as well as unbranded builds. > _And_, turns out, ESR releases (see below, and thank you for raising > that). > > In fairness, there may be substantial changes as this gets rolled out. In conversations today and yesterday, I pointed out that I liked Apple’s approach (before it had a mandatory charge) of signing a developer key and letting that be enough to sign all the extensions from the developer. Then I remembered something that Mozilla may be using as an object lesson here, specifically the case of the Apple/Dash controversy where a developer purportedly paid for a relative’s developer account, and one or more of those accounts were involved in app rating manipulation. http://daringfireball.net/2016/10/apple_dash_controversy I support code signing, but I’m not convinced that certifying the developer (who then signs the app) is a worse approach than signing each app. The latter sounds quite a bit more resource intensive for Mozilla. Deirdre _______________________________________________ svlug mailing list [email protected] http://lists.svlug.org/lists/listinfo/svlug