Open Bug 1409569 Opened 2 years ago Updated Last year

Enabling MITIGATION_FORCE_MS_SIGNED_BINS for content processes

Categories

(Core :: Security: Process Sandboxing, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: meta)

Filing this tracking bug for work to be done to enable MITIGATION_FORCE_MS_SIGNED_BINS for content processes on Windows.

We need to develop a strategy for getting core mozilla libraries loaded early or statically linked. It would be nice if we could do this as early as possible.
I know offhand one that we'll run into is libsoftokn3; unfortunately I think it intentionally is lazily loaded to assist startup performance.
(In reply to Alex Gaynor [:Alex_Gaynor] from comment #1)
> I know offhand one that we'll run into is libsoftokn3; unfortunately I think
> it intentionally is lazily loaded to assist startup performance.

This sounds to me like another data point in favor of having all lazy loading done by a single service, as opposed to ad-hoc places all over the code.
(In reply to Alex Gaynor [:Alex_Gaynor] from comment #1)
> I know offhand one that we'll run into is libsoftokn3; unfortunately I think
> it intentionally is lazily loaded to assist startup performance.

I can see why we might want to delay initializing softokn, but that might not apply to just pre-loading the library?

Also, it's theoretically possible to statically link all of NSS, but it'd need some changes in the NSS build system and some strategic use of PR_LoadStaticLibrary.  Chrome did this, back before they switched to BoringSSL, and there are even some patches hiding in Bugzilla somewhere (but they're kind of hacky, never landed in upstream NSS, and have certainly bitrotted).
Priority: -- → P3
Blocks: 1378417
Also, I think graphics drivers would be a problem here. We could ship this behind WebRender / WSCD possibly.
You need to log in before you can comment on or make changes to this bug.