firefox-58.0.1

[ken@…]

Fixes CVE-2018-5124, Arbitrary code execution through unsanitized browser UI

According to The Register, potential remote code execution after opening a malicious document or link.

[ken@…]

It built on my fast machine with 8 cores, but when I used a slower 4-core machine to check if the build was slower than before, it failed to compile the style cargo.

Retrying with --verbose it still fails, but reports a segmentation fault, invalid memory reference. That is with gcc-7.3 (which managed to build 58.0.

Possibly similar to ​https://github.com/rust-lang/rust/issues/45403 - what a heap of fetid dingo's kidneys

[ken@…]

I tried ac_add_options --disable-optimize but no backtrace.

I don't have any other recent desktops with a 7.3 version of g++. Retrying on the same machine with a build from December.

[ken@…]

swears - the build finished, but then it exited before installing. That is the sort of problem I had with rustc-1.23.0, but this is 1.22.1.

I should note that the machine with the segfault has had problems in the past - I suspect it lacks sufficient voltage for the RAM, with no option to change that - but it has been reliable since I started dropping the caches in an initscript. Maybe it will work on gcc-7.3.0 if I reduce the number of available CPUs with taskset : I'm trying that, it has now got past the compile of style, so possibly a local problem.

r19719