Bug 1329336 Block remote jar files by default draft
authorTom Ritter <tom@mozilla.com>
Wed, 05 Apr 2017 11:18:34 -0500
changeset 556324 62c64785d1aa2e5eb356a845143d2e3e12a9e17d
parent 556295 720b9177c6856c1c4339d0fac1bf5149c0d53950
child 622846 9ce9a77a77c699fa0ef12f7852be19b7bb86c8c1
push id52503
push userbmo:tom@mozilla.com
push dateWed, 05 Apr 2017 16:19:09 +0000
bugs1329336
milestone55.0a1
Bug 1329336 Block remote jar files by default MozReview-Commit-ID: CqmTk9ICHVF
modules/libpref/init/all.js
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -1695,22 +1695,17 @@ pref("network.websocket.delay-failed-rec
 // Equal to the DEFAULT_RECONNECTION_TIME_VALUE value in nsEventSource.cpp
 pref("dom.server-events.default-reconnection-time", 5000); // in milliseconds
 
 // If false, remote JAR files that are served with a content type other than
 // application/java-archive or application/x-jar will not be opened
 // by the jar channel.
 pref("network.jar.open-unsafe-types", false);
 // If true, loading remote JAR files using the jar: protocol will be prevented.
-#ifdef RELEASE_OR_BETA
-// Keep allowing remote JAR files for IBM iNotes (see bug 1255139) for now.
-pref("network.jar.block-remote-files", false);
-#else
 pref("network.jar.block-remote-files", true);
-#endif
 
 // This preference, if true, causes all UTF-8 domain names to be normalized to
 // punycode.  The intention is to allow UTF-8 domain names as input, but never
 // generate them from punycode.
 pref("network.IDN_show_punycode", false);
 
 // If "network.IDN.use_whitelist" is set to true, TLDs with
 // "network.IDN.whitelist.tld" explicitly set to true are treated as