←back to thread

Firefox 42 will not allow unsigned extensions

(wiki.mozilla.org)
288 points fernandotakai | 3 comments | 11 Aug 15 03:51 UTC | HN request time: 0.63s | source
Show context
RexRollman ◴[11 Aug 15 09:54 UTC] No.10039938[source]▶
And slowly, freedom everywhere was destroyed in the name of security.
replies(2): >>10040367 #>>10040636 #
coldpie ◴[11 Aug 15 13:00 UTC] No.10040636[source]▶
Firefox is open source. Disabling the signature check will probably be a one-line change. Yes, it's a much larger barrier to entry (building Firefox is not trivial), but it's not like IE or Chrome where you have no choice in the matter at all.
replies(1): >>10040932 #
1. rockdoe ◴[11 Aug 15 13:39 UTC] No.10040932[source]▶
building Firefox is not trivial

./mach bootstrap

./mach build

replies(1): >>10041430 #
2. rndgermandude ◴[11 Aug 15 14:46 UTC] No.10041430[source]▶
Yeah? You at the very least forgot to obtain the source code first somehow. What about build-dependencies, because ./mach bootstrap does not fully handle that?

Now please tell me how to do a Windows release-build with all release features enabled (except for official branding), aka. a ton of configure switches, and also please do it for my language using the official de locale, because neither the source tar.bz2 nor the hg you'd normally clone contains that. I'm starting from scratch of course. And suddenly it is less easy and trivial..

replies(1): >>10042388 #
3. azakai ◴[11 Aug 15 16:36 UTC] No.10042388[source]▶
As the link mentions, you don't need to build from source. Binary builds are provided that do not have this restriction, for those that want that.