diff options
| author | mseaborn@chromium.org <mseaborn@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-09 13:53:08 +0000 |
|---|---|---|
| committer | mseaborn@chromium.org <mseaborn@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-09 13:53:08 +0000 |
| commit | f6c52338609c76cf8b7b68fafd27834e48d10f90 (patch) | |
| tree | 222d30abca1647957183d684ba885d3d93ffba92 /media/video/capture/video_capture_device_unittest.cc | |
| parent | f52e9d89fde6240c2bb0ba4d2b7002eebc488474 (diff) | |
| download | chromium_src-f6c52338609c76cf8b7b68fafd27834e48d10f90.zip chromium_src-f6c52338609c76cf8b7b68fafd27834e48d10f90.tar.gz chromium_src-f6c52338609c76cf8b7b68fafd27834e48d10f90.tar.bz2 | |
Non-SFI NaCl: Avoid exposing validation caching key to Non-SFI nexes
This per-profile key is an extra input into the hashing that NaCl's
validation cache does.
Hiding this key means that even if we did accidentally expose
SetKnownToValidate() to Non-SFI nexes, the nexe wouldn't be able to
create a hole in the SFI NaCl sandbox.
We should hide this key to reduce the attacker's ability to generate
collisions in hash-based caching.
Also hide some other startup parameters that aren't relevant to Non-SFI
mode.
BUG=367263
TEST=browser_tests
R=jln@chromium.org
Review URL: https://codereview.chromium.org/275513002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269270 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/video/capture/video_capture_device_unittest.cc')
0 files changed, 0 insertions, 0 deletions