ToDo: diffs FF57-FF58 #302
Comments
bugzilla tickets
|
|
pref("security.sandbox.content.level", 4); // prev: 3 pref("security.tls.version.max", 4); // prev: 3 |
|
Thanks, I've updated the link: 183a624 |
https://dxr.mozilla.org/mozilla-central/source/browser/modules/SchedulePressure.jsm |
|
^^ we already make ALL 3rdparty cookies sessionOnly with |
|
Don't know. Just-in-Time Compilation for Javascript (JIT) has this reference. And the same german source from #244 (comment) says:
|
|
|
|
Yes, it is a workaround for browsers. |
|
.autoSubmit - IMO we can add the new one but I wouldn't move the old one to deprecated just yet simply because it will look a bit weird if they do rename it back and we'd have to move it back up from 9999. |
|
See: BrowserWorks/Waterfox#356 For a test, here there's a Parallel Mandelbrot computation window. |
No, it's a separate thing. The other report URLs are for when a user actually clicks on a button to manually send a report to Google. This new one will cause reports to be sent automatically when you encounter a Safe Browsing warning page, as long as you have previously opted into this (i.e. checkbox on the warning pages, off by default).
The IP will be removed since we'll be proxying the reports and sending them to Google from our proxy server's IP address. Initially, the information will be for the Safe Browsing team at Google to make the service better for Firefox users (they already get that data for Chrome users). |
let's just scratch that. It is what it is and that's good enough.
apart from
this is for CVE-2018-5115.
let's just remove it completely. I'm not even sure this made any sense in the 1st place because I think this was overwritten by the e10s system addon. Let's also remove 1106 + 1107 because changing them to anything higher than 1 doesn't seem to be supported yet anyway.
/* 24xx: disable Shared Memory (Spectre mitigation)
* [1] https://github.com/tc39/ecmascript_sharedmem/blob/master/TUTORIAL.md
* [2] https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/ ***/
user_pref("javascript.options.shared_memory", false);^^ if you want.
https://bugzilla.mozilla.org/show_bug.cgi?id=1317445 I've disabled it in my user.js because I block downloadable fonts with uBO and don't need this "timeline" with a swap period and shit. But it's probably not really necessary and ignoring it is fine too. |
👍 |
I assume they're just using the google url until they have finalized all the code, the format of the data, etc. |
Yes, that's the one.
@earthlng is right. We're not going to expose this in the UI until we've sorted the proxy. |
but isn't setting these prefs to default-block an unnecessary roadblock itself? |
no it's not, that's just part of the preparation for making Devtools a system addon. And since Telemetry is now locked to false in all Release versions and Devtools is still built-in at the moment it doesn't actually do anything other than just set the pref to true.
I agree but for once I didn't wanna bitch about it :)
do it. And thanks for finishing this |
|
shouldn't the version be 58-beta at the moment + until you release the final 58 shortly before Firefox 59 is released? |
v57.0 and v58.0 - 130 diffs ( 63 new, 42 gone, 25 different )
FF58 is scheduled for release 2018-01-23
new in v58.0:
reminder: when we do a 57 final, redo scratchpad clearing prefspermissions.default.*- 1379560 & 380637removed, renamed or hidden in v58.0:
changed in v58.0:
11011102051711101205ignore
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: