Closed Bug 1257276 Opened 4 years ago Closed 2 years ago

Allow specification of environment variables when creating child processes

Categories

(Core :: Security: Process Sandboxing, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1297740
Tracking Status
firefox48 --- affected

People

(Reporter: aklotz, Assigned: gcp)

References

Details

(Whiteboard: sb+)

Attachments

(1 file)

It would be nice to be able to specify the environment of a child process as we're creating it. This is not currently possible (at least in the sandboxed Windows case) because chromium always passes NULL to CreateProcess for the child process's environment.

Exposing this will require that some changes be made upstream.
The primary use case for this is to be able to specify TMP/TEMP/TMPDIR at process creation time, instead of having a window during process startup where those variables point to paths that are restricted by the sandbox.

This would probably help with the NVIDIA shader cache situation, but more importantly, allows me to remove some hacks that were added to the crash reporter.
Whiteboard: [sb?] → sb+
Priority: -- → P5
Whiteboard: sb+ → sb?
The most logical would be to support EnvironmentMap on Windows next to OS_POSIX. CreateProcess has an lpEnvironment that looks suitable.

Upstream (chromium) does not seem to support this.
Assignee: nobody → gpascutto
Priority: P5 → P2
Whiteboard: sb? → sb+
\o/ We're definitely going to need this if we're going to use the sandbox for the InjectEject bootstrap process.
Fixed by Bug 1297740.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1297740
You need to log in before you can comment on or make changes to this bug.