summaryrefslogtreecommitdiffstats
path: root/sandbox
Commit message (Collapse)AuthorAgeFilesLines
* Revert 128016 - Make sandbox explicitly block opening broker and sandboxed ↵jschuh@chromium.org2012-03-237-121/+10
| | | | | | | | | | | | | | | processes BUG=117627 BUG=119150 TEST=sbox_validation_tests Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=127795 Review URL: https://chromiumcodereview.appspot.com/9716027 TBR=jschuh@chromium.org Review URL: https://chromiumcodereview.appspot.com/9834065 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128583 0039d316-1c4b-4281-b951-d872f2087c98
* Make sandbox explicitly block opening broker and sandboxed processesjschuh@chromium.org2012-03-217-10/+121
| | | | | | | | | | BUG=117627 BUG=119150 TEST=sbox_validation_tests Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=127795 Review URL: https://chromiumcodereview.appspot.com/9716027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128016 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 127836 - Revert 127820 - Revert 127795 - Make sandbox explicitly ↵zmo@google.com2012-03-217-121/+10
| | | | | | | | | | | | | | | | | | | | | block opening broker and sandboxed processes BUG=119182 BUG=117627 BUG=119150 TEST=sbox_validation_tests Review URL: https://chromiumcodereview.appspot.com/9716027 TBR=jschuh@chromium.org Review URL: https://chromiumcodereview.appspot.com/9796002 TBR=zmo@google.com Review URL: https://chromiumcodereview.appspot.com/9801003 TBR=zmo@google.com Review URL: https://chromiumcodereview.appspot.com/9796005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127840 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 127820 - Revert 127795 - Make sandbox explicitly block opening broker ↵zmo@google.com2012-03-207-10/+121
| | | | | | | | | | | | | | | | | | and sandboxed processes BUG=119182 BUG=117627 BUG=119150 TEST=sbox_validation_tests Review URL: https://chromiumcodereview.appspot.com/9716027 TBR=jschuh@chromium.org Review URL: https://chromiumcodereview.appspot.com/9796002 TBR=zmo@google.com Review URL: https://chromiumcodereview.appspot.com/9801003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127836 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 127795 - Make sandbox explicitly block opening broker and sandboxed ↵zmo@google.com2012-03-207-121/+10
| | | | | | | | | | | | | | | processes BUG=119182 BUG=117627 BUG=119150 TEST=sbox_validation_tests Review URL: https://chromiumcodereview.appspot.com/9716027 TBR=jschuh@chromium.org Review URL: https://chromiumcodereview.appspot.com/9796002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127820 0039d316-1c4b-4281-b951-d872f2087c98
* Make sandbox explicitly block opening broker and sandboxed processesjschuh@chromium.org2012-03-207-10/+121
| | | | | | | | | BUG=117627 BUG=119150 TEST=sbox_validation_tests Review URL: https://chromiumcodereview.appspot.com/9716027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127795 0039d316-1c4b-4281-b951-d872f2087c98
* Fix sidestep licensessteveblock@chromium.org2012-03-206-114/+17
| | | | | | Review URL: http://codereview.chromium.org/9733004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127665 0039d316-1c4b-4281-b951-d872f2087c98
* Add sandbox/OWNERSdpranke@chromium.org2012-03-131-0/+4
| | | | | | | | | R=cpu@chromium.org, jschuh@chromium.org BUG=117608 Review URL: https://chromiumcodereview.appspot.com/9692012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126494 0039d316-1c4b-4281-b951-d872f2087c98
* If using the suid sandbox, but not using the seccomp sandbox, there is amarkus@chromium.org2012-03-121-4/+4
| | | | | | | | | | | | | | | | | | | | | | good chance that we will produce a zombie process inside of the new pid namespace. This happens, because we create a short-lived helper process when setting up the pid namespace, but the new "init" process never gets around to reaping this process. It would have reaped it, if it had received a SIGCHLD signal from any other process that died. But without the seccomp sandbox, that doesn't happen very frequently. This changelist reorders instructions so that we always look for dead children at least once, when starting the mainloop of the new "init" process. In doing so, we will always find and reap our dead helper process. BUG=109944 TEST=Run Chrome with the suid but without the seccomp sandbox, grep for "defunct" processes in the output of "ps auxw". There shouldn't be any. Review URL: https://chromiumcodereview.appspot.com/9661001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126188 0039d316-1c4b-4281-b951-d872f2087c98
* Reserve the bottom of the address space to prevent predictable alocations.jschuh@chromium.org2012-02-281-1/+24
| | | | | | | | BUG=113891 Review URL: http://codereview.chromium.org/9447078 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@123920 0039d316-1c4b-4281-b951-d872f2087c98
* Flakiness cleanup: disable remaining flaky tests in src/evan@chromium.org2012-02-151-2/+2
| | | | | | | | | | | See https://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/fcec09fc659f39a6 BUG=114386,109405,38404 TBR=sky Review URL: http://codereview.chromium.org/9405024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@122168 0039d316-1c4b-4281-b951-d872f2087c98
* Fixed a bogus compiler warning.markus@chromium.org2012-01-301-1/+1
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119752 0039d316-1c4b-4281-b951-d872f2087c98
* Calling clone(CLONE_NEWPID) results in the new pid namespace getting a new ↵markus@chromium.org2012-01-304-48/+346
| | | | | | | | | | | | | | | | | | | | | "init" process. This process is now resposible for reaping all child processes that no longer have a direct parent process. Often, failure to do this goes unnoticed, because our sandbox'd processes don't often fork other processes that then continue to turn into daemon processes. But there is no reason, why they couldn't occasionally do so. And in fact, the seccomp sandbox does do so for its trusted process. In the past, this would result in us having lots of uncollected zombie processes that only disappeared when the browser terminated. BUG=109944 TEST=Run Chrome with both the suid sandbox and the seccomp sandbox, open and close a few tabs, verify that we don't produce any zombie processes Review URL: https://chromiumcodereview.appspot.com/9295005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119746 0039d316-1c4b-4281-b951-d872f2087c98
* Eliminated memory growth issue by removing null objects from a list that was ↵erikghill@gmail.com2012-01-262-22/+18
| | | | | | | | accumulating them. Now, the objects are removed from the list when they are no longer needed, instead of being set to null.BUG=110459TEST=1. Go to any webpage 2. Go to a different webpage 3. Go back to step 1 and repeat many times. Before the fix pool_objects_ in win2k_threadpool grows with each new webpage visited. After the fix pool_objects_.size() is bounded even as new webpages are visited. Review URL: http://codereview.chromium.org/9243014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119287 0039d316-1c4b-4281-b951-d872f2087c98
* Fix memory dealocatiom mismatch by using scoped_ptr_malloccpu@chromium.org2012-01-122-8/+9
| | | | | | | | | | | - Flagged by almost all tools BUG=101717 TEST= sandbox tests in the waterfall are green. Review URL: http://codereview.chromium.org/9107029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@117476 0039d316-1c4b-4281-b951-d872f2087c98
* ake string_util::WriteInto() DCHECK() that the supplied |length_with_null| > ↵pkasting@chromium.org2011-11-294-34/+6
| | | | | | | | | | | | 1, meaning that the without-'\0' string is non-empty. This replaces the conditional code added recently that makes this case return NULL. It's easier to understand if it's simply an error to call WriteInto() in this case at all. Add DCHECK()s or conditionals as appropriate to callers in order to ensure this assertion holds. BUG=none TEST=none Review URL: http://codereview.chromium.org/8418034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112005 0039d316-1c4b-4281-b951-d872f2087c98
* Replace all usages of FRIEND_TEST() with FRIEND_TEST_ALL_PREFIXES()robertshield@chromium.org2011-11-292-11/+11
| | | | | | | | BUG=105287 TEST=NONE Review URL: http://codereview.chromium.org/8678017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111935 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup: Remove unneeded forward declarations in printing, sandbox, and skia.thestig@chromium.org2011-11-144-12/+9
| | | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/8538001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@109961 0039d316-1c4b-4281-b951-d872f2087c98
* Expose the sandbox related code through the content API. I did a bit of ↵jam@chromium.org2011-10-291-7/+2
| | | | | | | | | | | | | cleanup while I was doing this. -got rid of SandboxInitWrapper, since I didn't see a need to expose given that we can just expose sandbox::SandboxInterfaceInfo -got rid of the duplicated code to initialize the broker -since I made MainFunctionParams only have the sandbox struct on Windows, I also made the mac specific auto release pool behind an ifdef as well. It seemed odd to make something so mac specific compile on all platforms to save some #ifdefs. BUG=98716 Review URL: http://codereview.chromium.org/8414020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@107863 0039d316-1c4b-4281-b951-d872f2087c98
* Remove 'settings' type from gyp filesevan@chromium.org2011-09-221-1/+1
| | | | | | | | | | | It is not actually supported by gyp; the fact that it works is a bug that I am working on fixing. BUG=96629 Review URL: http://codereview.chromium.org/7889051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102306 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 100328 - Prevent the renderer from dying if launched under ↵jschuh@chromium.org2011-09-221-6/+2
| | | | | | | | | | | | | | App-V/SoftGrid. We found a better workaround, so removing this one. BUG=95888 Review URL: http://codereview.chromium.org/7857022 TBR=nsylvain@chromium.org Review URL: http://codereview.chromium.org/7988006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@102289 0039d316-1c4b-4281-b951-d872f2087c98
* These unit tests are flaky and the code is exercised in the integration tests.jschuh@chromium.org2011-09-122-67/+0
| | | | | | | | BUG=89325 TEST=None Review URL: http://codereview.chromium.org/7870006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100712 0039d316-1c4b-4281-b951-d872f2087c98
* Prevent the renderer from dying if launched under App-V/SoftGrid.nsylvain@chromium.org2011-09-091-2/+6
| | | | | | | | | | | | | A version of Microsoft Office launches chrome under a virtual environment, and this virtual environment does not allow us to reduce the integrity level on the renderer. Since it returns a fake error (ERROR_INVALID_HANDLE), we can trap it and continue execution anyway... until we find a better fix. BUG=95888 Review URL: http://codereview.chromium.org/7857022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100328 0039d316-1c4b-4281-b951-d872f2087c98
* Simplify chrome_exe_main_*.cc, moving as much of the code out as possible. ↵jam@chromium.org2011-08-313-12/+0
| | | | | | | | This is in preparation for moving the code in ChromeMain (and associated platform files) to a common place that can be used by both chrome and other embedders of content (i.e. content_shell). Included is a change to make the sandbox code not need an AtExitManager. This is necessary because content_shell would be just one exe, and we'd need to initialize the sandbox before calling ChromeMain, which is what would creat AtExitManager.I removed the code that printed the tcmalloc stacks in the OOM handler (i.e. r33993) under Windows. The issue is I wanted to move the OOM handling code to base to match the other platforms (in a long string of changes to make the startup code more sane, so I can share it with a browser built over content). When I tried moving the tcmalloc code to base, then I ran into a bunch of linker errors because a bunch of targets that depend on base don't depend on allocator. When I tried to add that to base, I ran into strange gyp errors (see patchset 2). I asked Jim/Eric and they said they don't use this data from dumps, and that most of the OOM minimdumps are in v8 heap anyways. When James get back, if he still uses this I can figure out how to put this back.BUG=90445 Review URL: http://codereview.chromium.org/7810005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@99032 0039d316-1c4b-4281-b951-d872f2087c98
* Don't crash on a NULL type-name from ObjectTypeInformation.jschuh@chromium.org2011-08-231-1/+1
| | | | | | | | BUG=93449 TEST=None. Review URL: http://codereview.chromium.org/7714003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97934 0039d316-1c4b-4281-b951-d872f2087c98
* Trying again to land OOM priority manager changes.gspencer@google.com2011-08-233-13/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | First landing failed because of an obscure problem with building linux_shared. This change passes the linux_shared trybot (and linux and linux_chromeos trybots). Changing OOM range to 0, 1000 and tweaking OOM algorithm. With this change, we now use the newer oom_score_adj file (with fallback to oom_adj when on a system that doesn't support it) so that we can take advantage of a finer range ([0, 1000] instead of [0, 15]). Also tweaked the OOM priority manager to prioritize things in a slightly different order, preferring (even more) not to kill tabs that the user has currently selected. Original review: http://codereview.chromium.org/7671033/ BUG=chromium-os:18421, chromium:65009 TEST=Ran on device, observed OOM adj values, forced OOM conditions to watch kills. Review URL: http://codereview.chromium.org/7708020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97888 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 97724 - Changing OOM range to 0, 1000 and tweaking OOM algorithm.mattm@chromium.org2011-08-223-33/+13
| | | | | | | | | | | | | | | | | | | | | With this change, we now use the newer oom_score_adj file (with fallback to oom_adj when on a system that doesn't support it) so that we can take advantage of a finer range ([0, 1000] instead of [0, 15]). Also tweaked the OOM priority manager to prioritize things in a slightly different order, preferring (even more) not to kill tabs that the user has currently selected. BUG=chromium-os:18421, chromium:65009 TEST=Ran on device, observed OOM adj values, forced OOM conditions to watch kills. Review URL: http://codereview.chromium.org/7671033 TBR=gspencer@google.com Review URL: http://codereview.chromium.org/7685030 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97728 0039d316-1c4b-4281-b951-d872f2087c98
* Changing OOM range to 0, 1000 and tweaking OOM algorithm.gspencer@google.com2011-08-223-13/+33
| | | | | | | | | | | | | | | | | | With this change, we now use the newer oom_score_adj file (with fallback to oom_adj when on a system that doesn't support it) so that we can take advantage of a finer range ([0, 1000] instead of [0, 15]). Also tweaked the OOM priority manager to prioritize things in a slightly different order, preferring (even more) not to kill tabs that the user has currently selected. BUG=chromium-os:18421, chromium:65009 TEST=Ran on device, observed OOM adj values, forced OOM conditions to watch kills. Review URL: http://codereview.chromium.org/7671033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97724 0039d316-1c4b-4281-b951-d872f2087c98
* Don't switch to RtlCreateUserThread until after lockdown.jschuh@chromium.org2011-08-121-0/+11
| | | | | | | | BUG=91413 TEST=None. Review URL: http://codereview.chromium.org/7552014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96558 0039d316-1c4b-4281-b951-d872f2087c98
* Handle STATUS_BUFFER_OVERFLOW return value from NtQueryObject().jschuh@chromium.org2011-08-112-2/+4
| | | | | | | | BUG=91386 TEST=None Review URL: http://codereview.chromium.org/7542026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96478 0039d316-1c4b-4281-b951-d872f2087c98
* Make sandbox target a settings target type to fix a linker error.craig.schlenter@chromium.org2011-08-111-1/+1
| | | | | | | | | BUG=92164 TEST=Clobber build compiles, trybots Review URL: http://codereview.chromium.org/7602016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96425 0039d316-1c4b-4281-b951-d872f2087c98
* Fixup bad include and usage of BASE_API, which should be BASE_EXPORT.darin@chromium.org2011-08-051-2/+2
| | | | | | | TBR=rvargas@chromium.org Review URL: http://codereview.chromium.org/7582007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95619 0039d316-1c4b-4281-b951-d872f2087c98
* Hook GetUserDefaultLCID () to prevent crashes on attempting to connect to ↵jschuh@chromium.org2011-08-027-10/+36
| | | | | | | | | | CSRSS after lockdown. BUG=91216 TEST=None. Review URL: http://codereview.chromium.org/7541034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95144 0039d316-1c4b-4281-b951-d872f2087c98
* Sandbox: Fix a style nit. No actual code change.rvargas@google.com2011-08-021-3/+4
| | | | | | | | BUG=NONE TEST=NONE Review URL: http://codereview.chromium.org/7546001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@95102 0039d316-1c4b-4281-b951-d872f2087c98
* seccomp: simplify enable/disable logicevan@chromium.org2011-07-291-23/+11
| | | | | | | | | | | | | | 1) Only compile in seccomp code at all if it's on a platform we intend to support (non-ChromeOS non-ARM non-Views Linux). 2) Move usage of seccomp code behind a define and usage of seccomp flags into a function call. The former helps catch bugs in the latter: it will be a link error if I accidentally break the enable/disable logic in code. Review URL: http://codereview.chromium.org/7519016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94784 0039d316-1c4b-4281-b951-d872f2087c98
* Disable UnloadDllTest.BaselineAvicapDllsergeyu@chromium.org2011-07-271-1/+1
| | | | | | | | | | BUG=80569 TEST=None TBR=cpu@chromium.org Review URL: http://codereview.chromium.org/7520004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94333 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enabling chrome-sandbox for Clang builds.glotov@google.com2011-07-271-2/+2
| | | | | | | | | | | As Clang now (since #13349 -- hans) supports asm .common directive, we may re-enable chrome-sandbox for Clang builds. BUG=chromium-os:16717, chromium:70871, chromium-os:88578 TEST=none Review URL: http://codereview.chromium.org/7233011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94271 0039d316-1c4b-4281-b951-d872f2087c98
* Warm up GetUserDefaultLangID before closing client ALPC connections.jschuh@chromium.org2011-07-261-0/+7
| | | | | | | | BUG=90492 TEST=Run Chrome on 32-bit Windows 7 or Vista Review URL: http://codereview.chromium.org/7461092 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94169 0039d316-1c4b-4281-b951-d872f2087c98
* Remove explicit keyword from multi-argument (w/o default values) constructorsdilmah@chromium.org2011-07-261-1/+1
| | | | | | | | | BUG=None TEST=None Review URL: http://codereview.chromium.org/7477008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94115 0039d316-1c4b-4281-b951-d872f2087c98
* Close all open ALPC client ports at lockdown.jschuh@chromium.org2011-07-2412-6/+154
| | | | | | | | | | Close out the CSRSS and LSASS ALPC client ports that are opened during initialization. BUG=58069 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.RunThreadPool Review URL: http://codereview.chromium.org/7490002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93827 0039d316-1c4b-4281-b951-d872f2087c98
* Add a sandbox API to allow closing open handles at lockdown. jschuh@chromium.org2011-07-2111-9/+613
| | | | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93274 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93308 Review URL: http://codereview.chromium.org/7253054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93321 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 93308 - Add a sandbox API to allow closing open handles at lockdown. jschuh@chromium.org2011-07-2111-602/+9
| | | | | | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93274 Review URL: http://codereview.chromium.org/7253054 TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/7473022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93315 0039d316-1c4b-4281-b951-d872f2087c98
* Add a sandbox API to allow closing open handles at lockdown. jschuh@chromium.org2011-07-2111-9/+602
| | | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93274 Review URL: http://codereview.chromium.org/7253054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93308 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 93274 - Add a sandbox API to allow closing open handles at lockdown. jschuh@chromium.org2011-07-2011-605/+9
| | | | | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/7471021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93284 0039d316-1c4b-4281-b951-d872f2087c98
* Add a sandbox API to allow closing open handles at lockdown. jschuh@chromium.org2011-07-2011-9/+605
| | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93274 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 93113 - Add a sandbox API to allow closing open handles at lockdown.jschuh@chromium.org2011-07-1911-582/+9
| | | | | | | | | | | | | | Reverting on suspicion that it's related to NaCl test breakage. BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/7462003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93128 0039d316-1c4b-4281-b951-d872f2087c98
* Add a sandbox API to allow closing open handles at lockdown.jschuh@chromium.org2011-07-1911-9/+582
| | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@93113 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 92887 - Add a sandbox API to allow closing open handles at lockdown.jschuh@chromium.org2011-07-1811-552/+9
| | | | | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/7398035 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92906 0039d316-1c4b-4281-b951-d872f2087c98
* Add a sandbox API to allow closing open handles at lockdown.jschuh@chromium.org2011-07-1811-9/+552
| | | | | | | | | BUG=58069 BUG=74242 TEST=sbox_integration_tests --gtest_filter=HandleCloserTests.* Review URL: http://codereview.chromium.org/7253054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92887 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 92563 - Had a bug in the handle table unit test. Added GetHandleName ↵jschuh@chromium.org2011-07-143-63/+23
| | | | | | | | | | | | | to fix the bug and make handle management easier. TEST=sbox_unittests --gtest_filter=HandleTable.* BUG=89325 Review URL: http://codereview.chromium.org/7346027 TBR=jschuh@chromium.org Review URL: http://codereview.chromium.org/7379001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92568 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-14 19:15:33 +0000