nsPluginHost::GetPluginTempDir should return a sandbox writeable temp (Linux)

RESOLVED INVALID

Status

()

Core
Plug-ins
P3
normal
RESOLVED INVALID
2 years ago
9 months ago

People

(Reporter: tedd, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: sb+)

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8767946 [details]
mkdir sandbox violation backtrace

Similar to Bug 1270018, nsPluginHost::GetPluginTempDir should return a directory that is created by the parent and writable by a sandboxed content process.

This would allow us to remove sys_mkdir from the seccomp whitelist.

Removing sys_mkdir leads to the attached crashes.
Blocks: 1202910

Comment 1

2 years ago
Haik, is this related to bug 1270018?
Flags: needinfo?(haftandilian)

Comment 2

2 years ago
It is related, but linux specific which isn't in use yet on linux. It's also tracked under our linux milestone.
Flags: needinfo?(haftandilian)

Updated

2 years ago
Priority: -- → P3

Updated

2 years ago
OS: Unspecified → Linux
Hardware: Unspecified → All

Comment 3

2 years ago
When we fix this we need to enable the code in bug 1270018 on linux, and open up access to that specific directory.

Updated

2 years ago
Summary: nsPluginHost::GetPluginTempDir should return a sandbox writeable temp → nsPluginHost::GetPluginTempDir should return a sandbox writeable temp (Linux)

Updated

2 years ago
Whiteboard: sblc2 → sblc3

Updated

a year ago
Whiteboard: sblc3 → sblc5

Updated

a year ago
Whiteboard: sblc5 → sblc4

Updated

a year ago
Whiteboard: sblc4 → sblc3
We allow write access to /tmp, and /tmp has the X11 sockets. So we do want to take a look at this, and probably at least block out the X11 dir.

Updated

a year ago
Whiteboard: sblc3 → sb+
Blocks: 1387593
|GetPluginTempDir| no longer exists so this is no longer a problem.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.