need test to verify sandboxing is enabled on socket process
Categories
(Core :: Networking, enhancement, P3)
Tracking
()
People
(Reporter: mjf, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
After sandboxing the socket process is complete, we need a test to make sure it is enabled.
Reporter | ||
Updated•4 years ago
|
Comment 1•4 years ago
|
||
I would like to know how I can verify that for each OS type (Windows, Ubuntu, Mac OS[, and android?]) for the feature testing process. Do you think this would be a valid test case?
Reporter | ||
Comment 2•4 years ago
|
||
(In reply to Bodea Daniel [:danibodea] from comment #1)
I would like to know how I can verify that for each OS type (Windows, Ubuntu, Mac OS[, and android?]) for the feature testing process. Do you think this would be a valid test case?
This bug is really calling for a unittest check to verify that the socket process is sandboxed when we think it should be, currently anytime the socket process is running w/o the environment variable MOZ_DISABLE_SOCKET_PROCESS_SANDBOX=1.
However, the sandboxing team may have ways to tell externally if the process is sandboxed, which might make for a valid step in the feature test process. Haik gave me a link to a python script to check if a PID is sandboxed:
https://gist.github.com/hafta/bca83004cdf7542dbf71b46e629ec0af
I don't know if that is valid on platforms besides macOS.
Updated•2 years ago
|
Updated•1 month ago
|
Description
•