Daniel Micay on Twitter: "@RichFelker I love how they even go out of the way to provide their own sigaltstack without a guard page, even though the base system already provides one with a guard page: https://t.co/5NURn8mC8I The code all insanity: https://t.co/w1sn4hLf4u It comes up as an issue again and again." / Twitter

This 💩 is exhibit A for why there is no __MUSL__. github.com/erlang/otp/blo

2

3

Feb 25, 2019

Replying to

Check out this insanity: github.com/mozilla/gecko-. The normal choices are a library being extracted to the file system or having it mapped directly from the apk by having it uncompressed. Instead, Firefox uses lazy loading by intercepting segfaults when libraries are used.

2

1

2

Replying to

and

Firefox is beyond hope in terms of hardening due to all the undefined behavior incompatible with mitigations, but in this case they're taking things even further and blocking improvements to the OS. They are literally overwriting a portion of libc with their hard-wired code...

1

2

Replying to

and

I love how they even go out of the way to provide their own sigaltstack without a guard page, even though the base system already provides one with a guard page: github.com/mozilla/gecko- The code all insanity: github.com/mozilla/gecko- It comes up as an issue again and again.

12:12 AM · Feb 25, 2019Twitter Web Client

Replying to

and

Oh, and since they load it like this, their code ends up as dirty pages in memory instead of having on-demand paging from shared objects on the filesystem either in the apk (uncompressed) or in the directory of automatically extracted libraries / executables (compressed in apk).

1

Replying to

and

Transmission of an apk is compressed so having a library uncompressed in the apk like Chromium doesn't waste bandwidth. The apk uses a bit more space on the device, but less than having it both compressed in the apk and extracted alongside it. Firefox's design choice is terrible.

1

Show replies

Conversation