/external/libcap-ng/libcap-ng-0.7/src/test/ |
thread_test.c | 15 printf("thread1 filled capabilities\n"); 19 printf("Capabilities missing when there should be some\n"); 23 printf("SUCCESS: Full capabilities reported\n"); 32 printf("thread2 getting capabilities\n"); 36 printf("Detected capabilities when there should not be any\n"); 41 printf("SUCCESS: No capabilities reported\n"); 48 printf("Testing thread separation of capabilities\n");
|
/external/chromium_org/chrome/test/chromedriver/ |
capabilities_unittest.cc | 5 #include "chrome/test/chromedriver/capabilities.h" 102 Capabilities capabilities; local 105 Status status = capabilities.Parse(caps); 107 ASSERT_TRUE(capabilities.IsAndroid()); 108 ASSERT_EQ("abc", capabilities.android_package); 112 Capabilities capabilities; local 115 Status status = capabilities.Parse(caps); 120 Capabilities capabilities local 128 Capabilities capabilities; local 137 Capabilities capabilities; local 155 Capabilities capabilities; local 167 Capabilities capabilities; local 179 Capabilities capabilities; local 193 Capabilities capabilities; local 203 Capabilities capabilities; local 213 Capabilities capabilities; local 225 Capabilities capabilities; local 236 Capabilities capabilities; local 249 Capabilities capabilities; local 260 Capabilities capabilities; local 272 Capabilities capabilities; local 293 Capabilities capabilities; local 303 Capabilities capabilities; local 321 Capabilities capabilities; local 333 Capabilities capabilities; local 341 Capabilities capabilities; local 369 Capabilities capabilities; local 390 Capabilities capabilities; local 406 Capabilities capabilities; local 418 Capabilities capabilities; local 430 Capabilities capabilities; local 446 Capabilities capabilities; local 461 Capabilities capabilities; local 472 Capabilities capabilities; local 486 Capabilities capabilities; local 502 Capabilities capabilities; local 524 Capabilities capabilities; local 532 Capabilities capabilities; local 542 Capabilities capabilities; local 554 Capabilities capabilities; local [all...] |
capabilities.cc | 5 #include "chrome/test/chromedriver/capabilities.h" 27 typedef base::Callback<Status(const base::Value&, Capabilities*)> Parser; 32 Capabilities* capabilities) { 40 Capabilities* capabilities) { 52 Capabilities* capabilities) { 64 Capabilities* capabilities) { [all...] |
/external/chromium_org/gpu/command_buffer/common/ |
capabilities.cc | 5 #include "gpu/command_buffer/common/capabilities.h" 9 Capabilities::Capabilities()
|
capabilities.h | 12 struct GPU_EXPORT Capabilities { 27 Capabilities();
|
/external/libcap-ng/libcap-ng-0.7/docs/ |
capng_clear.3 | 3 capng_clear \- clear chosen capabilities set 11 capng_clear sets to 0 all bits in the selected posix capabilities set. The options are CAPNG_SELECT_CAPS for the traditional capabilities, CAPNG_SELECT_BOUNDS for the bounding set, or CAPNG_SELECT_BOTH if clearing both is desired. 19 .BR capabilities (7)
|
capng_fill.3 | 3 capng_fill \- fill chosen capabilities set 11 capng_fill sets all bits to a 1 in the selected posix capabilities set. The options are CAPNG_SELECT_CAPS for the traditional capabilities, CAPNG_SELECT_BOUNDS for the bounding set, or CAPNG_SELECT_BOTH if filling both is desired. 19 .BR capabilities (7)
|
capng_have_capabilities.3 | 3 capng_have_capabilities \- general check for capabilities 11 capng_have_capabilities will check the selected internal capabilities sets to see what the status is. The capabilities sets must be previously setup with calls to capng_get_caps_process, capng_get_caps_fd, or in some other way setup. The options are CAPNG_SELECT_CAPS for the traditional capabilities, CAPNG_SELECT_BOUNDS for the bounding set, or CAPNG_SELECT_BOTH if clearing both is desired. 22 .BR capabilities (7)
|
capng_setpid.3 | 11 capng_pid sets the working pid for capabilities operations. This is useful if you want to get the capabilities of a different process. 20 .BR capabilities (7)
|
capng_apply.3 | 3 capng_apply \- apply the stored capabilities settings 11 capng_apply will transfer the specified internal posix capabilities settings to the kernel. The options are CAPNG_SELECT_CAPS for the traditional capabilities, CAPNG_SELECT_BOUNDS for the bounding set, or CAPNG_SELECT_BOTH if transferring both is desired. 19 If you are doing multi-threaded programming, calling this function will only set capabilities on the calling thread. All other threads are unaffected. If you want to set overall capabilities for a multi-threaded process, you will need to do that before creating any threads. See the capset syscall for more information on this topic. 25 .BR capabilities (7)
|
capng_get_caps_process.3 | 3 capng_get_caps_process \- get the capabilities from a process 11 capng_get_caps_process will get the capabilities and bounding set of the pid stored inside libcap-ng's state table. The default is the pid of the running process. This can be changed by using the capng_setpid function. 19 If you are doing multi-threaded programming, calling this function will only get capabilities on the calling thread. If you want to get overall capabilities for a multi-threaded process, you can only do that before creating any threads. Afterwards, threads may be able to independantly set capabilities. 24 .BR capabilities (7)
|
capng_set_caps_fd.3 | 11 This function will write the file based capabilities to the extended attributes of the file that the descriptor was opened against. The bounding set is not included in file based capabilities operations. Note that this function will only work if compiled on a kernel that supports file based capabilities such as 2.6.2 21 .BR capabilities (7)
|
capng_get_caps_fd.3 | 11 This function will read the file based capabilities stored in extended attributes of the file that the descriptor was opened against. The bounding set is not included in file based capabilities operations. Note that this function will only work if compiled on a kernel that supports file based capabilities such as 2.6.26 and later. If the "magic" bit is set, then all effect capability bits are set. Otherwise the bits are cleared. 20 .BR capabilities (7)
|
/external/libcap-ng/libcap-ng-0.7/utils/ |
filecap.8 | 3 filecap \- a program to see capabilities 7 \fBfilecap\fP is a program that prints out a report of programs with file based capabilities. If a file is not in the report or there is no report at all, no capabilities were found. For expedience, the default is to check only the directories in the PATH environmental variable. If the \-a command line option is given, then all directories will be checked. If a directory is passed, it will recursively check that directory. If a path to a file is given, it will only check that file. If the path to the file includes capabilities, then they are written to the file. 12 This tells the program to show all capabilities starting from the / directory. Normally the PATH environmental variable is used to show you capabilities on files you are likely to execute. 15 This dumps all capabilities for reference. 19 .B To check file capabilities in $PATH: 22 .B To check file capabilities of whole system: 25 .B To check file capabilities recursively in a directory [all...] |
pscap.8 | 3 pscap \- a program to see capabilities 7 \fBpscap\fP is a program that prints out a report of process capabilities. If the application has any capabilities, it will be in the report with the exception of init. By giving the \-a command line option, init will be included, too. If a process is not in the report, it has dropped all capabilities. If the process has partial capabilities, it is further examined to see if it has an open-ended bounding set. If this is found to be true, a '+' symbol is added. 12 .BR capabilities (7),
|
captest.8 | 3 captest \- a program to demonstrate capabilities 7 \fBcaptest\fP is a program that demonstrates and prints out the current process capabilities. Each option prints the same report. It will output current capabilities. then it will try to access /etc/shadow directly to show if that can be done. Then it creates a child process that attempts to read /etc/shadow and outputs the results of that. Then it outputs the capabilities that a child process would have. 9 You can also apply file system capabilities to this program to study how they work. For example, filecap /usr/bin/captest chown. Then run captest as a normal user. Another interesting test is to make captest suid root so that you can see what the interaction is between root's credentials and capabilities. For example, chmod 4755 /usr/bin/captest. When run as a normal user, the program will see if privilege escalation is possible. But do not leave this app setuid root after you are don testing so that an attacker cannot take advantage of it. 14 This drops all capabilities and clears the bounding set. 17 This drops just traditional capabilities. 23 This option outputs the effective capabilities in text rather than numerically. 30 .BR capabilities (7 [all...] |
netcap.8 | 3 netcap \- a program to see capabilities 7 \fBnetcap\fP is a program that prints out a report of process capabilities. If the application is using tcp, udp, raw, or packet family of sockets AND has any capabilities, it will be in the report. If the process has partial capabilities, it is further examined to see if it has an open-ended bounding set. If this is found to be true, a '+' symbol is added. 14 .BR capabilities (7),
|
/external/chromium_org/cc/output/ |
context_provider.cc | 11 ContextProvider::Capabilities::Capabilities()
|
/external/chromium_org/remoting/client/ |
chromoting_client.cc | 8 #include "remoting/base/capabilities.h" 56 const std::string& capabilities) { 59 local_capabilities_ = capabilities; 71 const protocol::Capabilities& capabilities) { 74 // Only accept the first |protocol::Capabilities| message. 76 LOG(WARNING) << "protocol::Capabilities has been received already."; 81 if (capabilities.has_capabilities()) 82 host_capabilities_ = capabilities.capabilities(); 162 protocol::Capabilities capabilities; local [all...] |
/external/chromium_org/sandbox/win/src/ |
app_container_unittest.cc | 34 // Tests handling of security capabilities on the attribute list. 40 std::vector<base::string16> capabilities; local 42 attributes->SetAppContainer(L"S-1-foo", capabilities)); 45 attributes->SetAppContainer(L"S-1-15-2-12345-234", capabilities)); 49 capabilities.push_back(L"S-1-15-3-12345678-87654321"); 50 capabilities.push_back(L"S-1-15-3-1"); 51 capabilities.push_back(L"S-1-15-3-2"); 52 capabilities.push_back(L"S-1-15-3-3"); 54 attributes->SetAppContainer(L"S-1-15-2-1-2", capabilities));
|
/external/chromium_org/remoting/android/java/src/org/chromium/chromoting/ |
Capabilities.java | 8 * The list of all capabilities that might be supported by the Chromoting host 9 * and client. As more capabilities are supported on the android client, 13 public class Capabilities {
|
/external/chromium_org/remoting/base/ |
capabilities.h | 14 // Returns true if |capabilities| contain capability |key|. 15 bool HasCapability(const std::string& capabilities, const std::string& key); 17 // Returns a set of capabilities contained in both |client_capabilities| and
|
/external/chromium_org/chrome/browser/resources/print_preview/data/ |
capabilities_holder.js | 14 * Reference to the capabilities object. 28 * @param {!print_preview.Cdd} capabilities New instance to put into the 31 set: function(capabilities) { 32 this.capabilities_ = capabilities;
|
/external/deqp/framework/egl/ |
egluNativeDisplay.cpp | 31 NativeDisplay::NativeDisplay (Capability capabilities, EGLenum platformType, const char* platformExtension) 32 : m_capabilities (capabilities) 37 DE_ASSERT(capabilities & CAPABILITY_GET_DISPLAY_PLATFORM); 40 NativeDisplay::NativeDisplay (Capability capabilities) 41 : m_capabilities (capabilities) 45 DE_ASSERT(!(capabilities & CAPABILITY_GET_DISPLAY_PLATFORM)); 46 DE_ASSERT(capabilities & CAPABILITY_GET_DISPLAY_LEGACY); 67 NativeDisplayFactory::NativeDisplayFactory (const std::string& name, const std::string& description, NativeDisplay::Capability capabilities, EGLenum platformType, const char* platformExtension) 69 , m_capabilities (capabilities) 74 DE_ASSERT(capabilities & NativeDisplay::CAPABILITY_GET_DISPLAY_PLATFORM) [all...] |
/packages/services/Telephony/src/com/android/services/telephony/ |
GsmConnection.java | 60 int capabilities = super.buildConnectionCapabilities(); local 61 capabilities |= CAPABILITY_MUTE; 62 capabilities |= CAPABILITY_SUPPORT_HOLD; 64 capabilities |= CAPABILITY_HOLD; 66 return capabilities;
|