| /external/chromium_org/ |
| WATCHLISTS | 342 'filepath': 'sandbox/linux/',
345 'filepath': 'content/common/sandbox.*linux.cc',
[all...] |
| /external/chromium_org/components/breakpad/app/ |
| breakpad_win.cc | 35 #include "sandbox/win/src/nt_internals.h"
36 #include "sandbox/win/src/sidestep/preamble_patcher.h"
|
| /external/chromium_org/components/nacl/browser/ |
| nacl_browser.cc | 126 // allow a NaCl inner sandbox escape.
140 // to an extension directory could allow an outer sandbox escape. openat(...)
|
| /frameworks/base/docs/html/guide/topics/security/ |
| permissions.jd | 51 the basic sandbox. Applications statically declare the permissions they
57 <p>The application sandbox does not depend on the technology used to build
|
| /external/chromium/chrome/common/ |
| chrome_switches.cc | 213 // Disables the sandbox for the built-in flash player.
214 const char kDisableFlashSandbox[] = "disable-flash-sandbox";
[all...] |
| /external/chromium_org/content/ |
| content_browser.gypi | [all...] |
| content_tests.gypi | 242 '../sandbox/sandbox.gyp:sandbox',
[all...] |
| /external/chromium_org/third_party/WebKit/Source/core/frame/ |
| ContentSecurityPolicy.cpp | 145 static const char sandbox[] = "sandbox"; member in namespace:WebCore::__anon13379
165 || equalIgnoringCase(name, sandbox)
[all...] |
| /external/chromium_org/chrome/browser/ui/webui/ |
| about_ui.cc | 830 // The setuid sandbox is required as our first-layer sandbox.
834 // A second-layer sandbox is also required to be adequately sandboxed.
[all...] |
| /external/chromium_org/chrome/renderer/ |
| chrome_content_renderer_client.cc | [all...] |
| /external/chromium_org/net/http/ |
| transport_security_state_static.h | 401 {25, true, "\004plus\007sandbox\006google\003com", true, kGooglePins, DOMAIN_GOOGLE_COM },
[all...] |
| transport_security_state_static.json | 180 { "name": "plus.sandbox.google.com", "include_subdomains": true, "mode": "force-https", "pins": "google" },
513 { "name": "sandbox.mydigipass.com", "mode": "force-https" },
514 { "name": "www.sandbox.mydigipass.com", "mode": "force-https" },
[all...] |
| /external/chromium/base/win/ |
| pe_image.cc | 211 // This may be called by sandbox before MSVCRT dll loads, so can't use
|
| /external/chromium/chrome/browser/ |
| crash_handler_host_linux.cc | 68 // sending datagrams to other sockets on the system. The sandbox may prevent
|
| /external/chromium/chrome/browser/task_manager/ |
| task_manager.h | 56 SANDBOX_HELPER, // A sandbox helper process.
|
| /external/chromium_org/base/win/ |
| pe_image.cc | 212 // This may be called by sandbox before MSVCRT dll loads, so can't use
|
| /external/chromium_org/build/android/gyp/ |
| generate_v14_compatible_resources.py | 132 # https://plus.sandbox.google.com/+RomanNurik/posts/huuJd8iVVXY?e=Showroom
|
| /external/chromium_org/chrome/browser/ |
| process_singleton_win.cc | 236 // Microsoft's Softricity virtualization breaks the sandbox processes.
|
| /external/chromium_org/chrome/common/ |
| chrome_utility_messages.h | 168 // sandbox.
|
| logging_chrome.cc | 280 // ALPC handle after sandbox lockdown on Windows.
|
| /external/chromium_org/chrome/common/extensions/docs/server2/test_data/github_file_system/test_owner/repo/commits/ |
| HEAD | 124 "patch": "@@ -1,6 +1,6 @@\n ## Overview of Chrome In App Payments API\n \n-You can use the Chrome In App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome Wallet App (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n+You can use the Chrome In-App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome In-App Payments Service (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n \n ## Sample app\n Here?s a sample app that calls into the Chrome IAP API and provides options to trigger payments via the sandbox server as well as the production server:"
|
| /external/chromium_org/chrome/installer/linux/debian/ |
| build.sh | 109 for x in chrome chrome-sandbox locales; do
|
| /external/chromium_org/components/breakpad/browser/ |
| crash_handler_host_linux.cc | 91 // sending datagrams to other sockets on the system. The sandbox may prevent
|
| /external/chromium_org/content/renderer/ |
| render_thread_impl.h | 439 // Initialize COM when using plugins outside the sandbox.
|
| /external/chromium_org/gpu/config/ |
| software_rendering_list_json.cc | 895 "description": "Accelerated video decode interferes with GPU sandbox on older Intel drivers",
|
