Open Bug 1593389 Opened 6 years ago Updated 11 months ago

[meta] Use different executables for different child process types

Categories

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

Unspecified
macOS
enhancement

Tracking

()

People

(Reporter: haik, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

Using different executables instead of the same plugin-container binary would allow us to use different entitlements for web content and plugin processes. Web/file content processes should not have to load any libraries not signed by Apple or Mozilla (unlike Widevine or Flash plugin processes) so this would allow us to use the more strict entitlement that prevents loading of libraries not signed by Apple or the same team ID as the application. See also bug 1529390.

Priority: -- → P2
Severity: normal → S3
Assignee: nobody → haftandilian
Priority: P2 → P1
Assignee: haftandilian → nobody
Keywords: meta
Summary: [macOS] Use different executables for different child process types → [meta] Use different executables for different child process types
Depends on: 1827747
Depends on: 1593072

We now have support in our release and codesigning pipeline to use different executables with different entitlements for different child process types. This was used to ship bug 1827747. Content processes and GMP processes now use different executables with different entitlements.

Depends on: 1901882
You need to log in before you can comment on or make changes to this bug.