1027907 - Use `SetIntegrityLevel` instead of `SetDelayedIntegrityLevel` for content processes

Status: RESOLVED FIXED

(Core :: Security, defect)

Description

[Tim Abraldes [:TimAbraldes] [:tabraldes]]

See bug 1011491 comment 0 and bug 1011491 comment 5 for rationale.

Comment 1

[Justin Schuh]

After looking at your usage I wrote a CL to make SetIntegrityLevel work out of the box for the alternate desktop: https://codereview.chromium.org/330853002/

I'm not sure how much your code has branched, but you might want roll forward after it lands, or merge it in.

Comment 2

[Tim Abraldes [:TimAbraldes] [:tabraldes]]

(In reply to Justin Schuh from comment #1)
> After looking at your usage I wrote a CL to make SetIntegrityLevel work out
> of the box for the alternate desktop:
> https://codereview.chromium.org/330853002/

Thanks Justin! That's really great of you.

> I'm not sure how much your code has branched, but you might want roll
> forward after it lands, or merge it in.

The code seems to be pretty well isolated, thanks I think to Brian Bondy [:bbondy] who did the initial legwork for integrating the sandbox code. Rolling forward seems like the best course of action here.

Comment 3

[Justin Schuh]

No problem. The change landed today, so you should be able to roll your code forward.

Comment 4

[Bob Owen (:bobowen)]

This was essentially done as part of the changes for bug 1149483 and bug 1151767