Linux ns8.secondary29.go.th 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64
Apache/2.2.15 (CentOS)
: 122.154.134.11 | : 122.154.134.9
Cant Read [ /etc/named.conf ]
5.6.40
apache
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
openscap /
schemas /
oval /
5.9 /
[ HOME SHELL ]
Name
Size
Permission
Action
aix-definitions-schema.xsd
48.18
KB
-rw-r--r--
aix-system-characteristics-sch...
23.92
KB
-rw-r--r--
apache-definitions-schema.xsd
13.27
KB
-rw-r--r--
apache-system-characteristics-...
5.63
KB
-rw-r--r--
catos-definitions-schema.xsd
35.63
KB
-rw-r--r--
catos-system-characteristics-s...
15.72
KB
-rw-r--r--
esx-definitions-schema.xsd
49.31
KB
-rw-r--r--
esx-system-characteristics-sch...
20.16
KB
-rw-r--r--
freebsd-definitions-schema.xsd
10.87
KB
-rw-r--r--
freebsd-system-characteristics...
5.65
KB
-rw-r--r--
hpux-definitions-schema.xsd
59.89
KB
-rw-r--r--
hpux-system-characteristics-sc...
19.01
KB
-rw-r--r--
independent-definitions-schema...
206.94
KB
-rw-r--r--
independent-system-characteris...
65.44
KB
-rw-r--r--
ios-definitions-schema.xsd
54.99
KB
-rw-r--r--
ios-system-characteristics-sch...
22.42
KB
-rw-r--r--
linux-definitions-schema.xsd
133.99
KB
-rw-r--r--
linux-system-characteristics-s...
81.4
KB
-rw-r--r--
macos-definitions-schema.xsd
85.58
KB
-rw-r--r--
macos-system-characteristics-s...
40.42
KB
-rw-r--r--
oval-common-schema.xsd
66.58
KB
-rw-r--r--
oval-definitions-schema.xsd
153.28
KB
-rw-r--r--
oval-definitions-schematron.xs...
329.64
KB
-rw-r--r--
oval-directives-schema.xsd
7.45
KB
-rw-r--r--
oval-directives-schematron.xsl
64.58
KB
-rw-r--r--
oval-results-schema.xsd
64.35
KB
-rw-r--r--
oval-results-schematron.xsl
64.52
KB
-rw-r--r--
oval-system-characteristics-sc...
53.2
KB
-rw-r--r--
oval-system-characteristics-sc...
29.43
KB
-rw-r--r--
oval-variables-schema.xsd
6.95
KB
-rw-r--r--
oval-variables-schematron.xsl
6.62
KB
-rw-r--r--
pixos-definitions-schema.xsd
16.15
KB
-rw-r--r--
pixos-system-characteristics-s...
6.81
KB
-rw-r--r--
sharepoint-definitions-schema....
163.35
KB
-rw-r--r--
sharepoint-system-characterist...
88.56
KB
-rw-r--r--
solaris-definitions-schema.xsd
76.28
KB
-rw-r--r--
solaris-system-characteristics...
34.31
KB
-rw-r--r--
unix-definitions-schema.xsd
221.72
KB
-rw-r--r--
unix-system-characteristics-sc...
113.11
KB
-rw-r--r--
windows-definitions-schema.xsd
673.83
KB
-rw-r--r--
windows-system-characteristics...
289.62
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : unix-system-characteristics-schema.xsd
<?xml version="1.0" encoding="utf-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:unix-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#unix" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#unix" elementFormDefault="qualified" version="5.9"> <xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" schemaLocation="oval-system-characteristics-schema.xsd"/> <xsd:annotation> <xsd:documentation>The following is a description of the elements, types, and attributes that compose the UNIX specific system characteristic items found in Open Vulnerability and Assessment Language (OVAL). Each item is an extension of the standard item element defined in the Core System Characteristic Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL Items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core System Characteristic Schema is not outlined here.</xsd:documentation> <xsd:documentation>The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.</xsd:documentation> <xsd:appinfo> <schema>Unix System Characteristics</schema> <version>5.9</version> <date>2/22/2011 10:52:27 AM</date> <terms_of_use>Copyright (c) 2002-2011, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.</terms_of_use> <sch:ns prefix="oval-sc" uri="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5"/> <sch:ns prefix="unix-sc" uri="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#unix"/> <sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/> </xsd:appinfo> </xsd:annotation> <!-- =============================================================================== --> <!-- ============================= DNS CACHE ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="dnscache_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The dnscache_item stores information retrieved from the DNS cache about a domain name, its time to live, and its corresponding IP addresses.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="domain_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The domain_name element contains a string that represents a domain name that was collected from the DNS cache on the local system.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ttl" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The ttl element contains an integer that represents the time to live in seconds of the DNS cache entry.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ip_address" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The ip_address element contains a string that represents an IP address associated with the specified domain name. Note that the IP address can be IPv4 or IPv6.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ================================= FILE ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="file_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The file item holds information about the individual files found on a system. Each file item contains path and filename information as well as its type, associated user and group ids, relevant dates, and the privialeges granted. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>The name of the file. If the xsi:nil attribute is set to true, then the item being represented is the higher directory represented by the path entity.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the file's type: regular file (regular), directory, named pipe (fifo), symbolic link, socket or block special.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="group_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the group owner of the file, by group number.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The numeric user id, or uid, is the third column of each user's entry in /etc/passwd. This element represents the owner of the file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="a_time" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time that the file was last accessed, in seconds since the Unix epoch. The Unix epoch is the time 00:00:00 UTC on January 1, 1970.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="c_time" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of the last change to the file's inode, in seconds since the Unix epoch. The Unix epoch is the time 00:00:00 UTC on January 1, 1970. An inode is a Unix data structure that stores all of the information about a particular file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="m_time" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of the last change to the file's contents, in seconds since the Unix epoch. The Unix epoch is the time 00:00:00 UTC on January 1, 1970.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="size" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the size of the file in bytes.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="suid" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Does the program run with the uid (thus privileges) of the file's owner, rather than the calling user?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="sgid" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Does the program run with the gid (thus privileges) of the file's group owner, rather than the calling user's group?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="sticky" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can users delete each other's files in this directory, when said directory is writable by those users?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="uread" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the owner (user owner) of the file read this file or, if a directory, read the directory contents?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="uwrite" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the owner (user owner) of the file write to this file or, if a directory, write to the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="uexec" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the owner (user owner) of the file execute it or, if a directory, change into the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="gread" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the group owner of the file read this file or, if a directory, read the directory contents?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="gwrite" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the group owner of the file write to this file, or if a directory, write to the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="gexec" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the group owner of the file execute it or, if a directory, change into the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="oread" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can all other users read this file or, if a directory, read the directory contents?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="owrite" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the other users write to this file, or if a directory, write to the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="oexec" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the other users execute this file or, if a directory, change into the directory?</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="has_extended_acl" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Does the file or directory have ACL permissions applied to it? If the file or directory doesn't have an ACL, or it matches the standard UNIX permissions, the value will be 'false'. Otherwise, if a file or directory has an ACL, the value will be 'true'. If the system does not support ACLs, the status will be 'does not exist' and if the system supports ACLs, the status will be 'exists'.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ========================= FILE EXTENDED ATTRIBUTE ITEM ===================== --> <!-- =============================================================================== --> <xsd:element name="fileextendedattribute_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The file extended attribute item holds information about the individual file extended attributes found on a system. Each file extended attribute item contains path, filename, and attribute name information as well as the attribute's value. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The filepath element specifies the absolute path for a file on the machine. A directory cannot be specified as a filepath.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The path element specifies the directory component of the absolute path to a file on the machine.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>The name of the file. If the xsi:nil attribute is set to true, then the item being represented is the higher directory represented by the path entity.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="attribute_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the extended attribute's name, identifier or key.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the extended attribute's value or contents.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ================================== GCONF ITEM ============================== --> <!-- =============================================================================== --> <xsd:element name="gconf_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The gconf_item holds information about an individual GConf preference key found on a system. Each gconf_item contains a preference key, source, type, whether it's writable, the user who last modified it, the time it was last modified, whether it's the default value, as well as the preference key's value. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="key" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The preference key to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="source" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>The source used to look up the preference key.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="type" type="unix-sc:EntityItemGconfTypeType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The type of the preference key.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="is_writable" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Is the preference key writable? If true, the preference key is writable. If false, the preference key is not writable.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mod_user" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The user who last modified the preference key.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mod_time" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The time the preference key was last modified in seconds since the Unix epoch. The Unix epoch is the time 00:00:00 UTC on January 1, 1970.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="is_default" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Is the preference key value the default value. If true, the preference key value is the default value. If false, the preference key value is not the default value.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The value of the preference key.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ================================ INETD ITEM ================================= --> <!-- =============================================================================== --> <xsd:element name="inetd_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The inetd item holds information associated with different Internet services. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="protocol" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>A recognized protocol listed in the file /etc/inet/protocols.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="service_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of a valid service listed in the services file. For RPC services, the value of the service-name field consists of the RPC service name or program number, followed by a '/' (slash) and either a version number or a range of version numbers (for example, rstatd/2-4).</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="server_program" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Either the pathname of a server program to be invoked by inetd to perform the requested service, or the value internal if inetd itself provides the service.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="server_arguments" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="endpoint_type" type="unix-sc:EntityItemEndpointType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="exec_as_user" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="wait_status" type="unix-sc:EntityItemWaitStatusType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This field has values wait or nowait. This entry specifies whether the server that is invoked by inetd will take over the listening socket associated with the service, and whether once launched, inetd will wait for that server to exit, if ever, before it resumes listening for new service requests.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================== INTERFACE ITEM =============================== --> <!-- =============================================================================== --> <xsd:element name="interface_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The interface item holds information about the interfaces on a system. Each interface item contains name and address information as well as any associated flags. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name entity is the actual name of the specific interface. Examples might be eth0, eth1, fwo, etc.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="type" type="unix-sc:EntityItemInterfaceType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This element specifies the type of interface.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="hardware_addr" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The hardware_addr entity is the hardware or MAC address of the physical network card. MAC addresses should be formatted according to the IEEE 802-2001 standard which states that a MAC address is a sequence of six octet values, separated by hyphens, where each octet is represented by two hexadecimal digits. Uppercase letters should also be used to represent the hexadecimal digits A through F.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="inet_addr" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The inet_addr entity is the IP address of the specific interface. Note that the IP address can be IPv4 or IPv6. If the IP address is an IPv6 address, this entity should be expressed as an IPv6 address prefix using CIDR notation and the netmask entity should not be collected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="broadcast_addr" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The broadcast_addr entity is the broadcast IP address for this interface's network. Note that the IP address can be IPv4 or IPv6.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="netmask" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the bitmask used to calculate the interface's IP network. The network number is calculated by bitwise-ANDing this with the IP address. The host number on that network is calculated by bitwise-XORing this with the IP address. Note that if the inet_addr entity contains an IPv6 address prefix, this entity should not be collected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="flag" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>This is the interface flag line, which generally contains flags like "UP" to denote an active interface, "PROMISC" to note that the interface is listening for Ethernet frames not specifically addressed to it, and others.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================== PASSWORD ITEM =============================== --> <!-- =============================================================================== --> <xsd:element name="password_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>/etc/passwd. See passwd(4).</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="username" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the user for which data was gathered.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="password" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the encrypted version of the user's password.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The numeric user id, or uid, is the third column of each user's entry in /etc/passwd. This element represents the owner of the file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="group_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the group owner of the file, by group number.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="gcos" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="home_dir" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="login_shell" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================== PROCESS ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="process_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>Output of /usr/bin/ps. See ps(1).</xsd:documentation> <xsd:appinfo> <oval:deprecated_info> <oval:version>5.8</oval:version> <oval:reason>The process_item has been deprecated and replaced by the process58_item. The entity 'command' was changed to 'command_line' in the process58_item to accurately describe what information is collected. Please see the process58_item for additional information.</oval:reason> </oval:deprecated_info> <sch:pattern id="unix-sc_processitem_dep"> <sch:rule context="unix-sc:process_item"> <sch:report test="true()">DEPRECATED ITEM: <sch:value-of select="name()"/> ID: <sch:value-of select="@id"/></sch:report> </sch:rule> </sch:pattern> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="command" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This specifies the command/program name about which data has has been collected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exec_time" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the cumulative CPU time, formatted in [DD-]HH:MM:SS where DD is the number of days when execution time is 24 hours or more.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="pid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ppid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process's parent process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="priority" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the scheduling priority with which the process runs. This can be adjusted with the nice command or nice() system call.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ruid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the real user id which represents the user who has created the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="scheduling_class" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>A platform specific characteristic maintained by the scheduler: RT (real-time), TS (timeshare), FF (fifo), SYS (system), etc.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="start_time" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of day the process started formatted in HH:MM:SS if the same day the process started or formatted as MMM_DD (Ex.: Feb_5) if process started the previous day or further in the past.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="tty" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TTY on which the process was started, if applicable.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the effective user id which represents the actual privileges of the process.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================= PROCESS ITEM (58) ============================== --> <!-- =============================================================================== --> <xsd:element name="process58_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>Output of /usr/bin/ps. See ps(1).</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="command_line" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the string used to start the process. This includes any parameters that are part of the command line.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exec_time" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the cumulative CPU time, formatted in [DD-]HH:MM:SS where DD is the number of days when execution time is 24 hours or more.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="pid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ppid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process's parent process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="priority" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the scheduling priority with which the process runs. This can be adjusted with the nice command or nice() system call.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ruid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the real user id which represents the user who has created the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="scheduling_class" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>A platform specific characteristic maintained by the scheduler: RT (real-time), TS (timeshare), FF (fifo), SYS (system), etc.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="start_time" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of day the process started formatted in HH:MM:SS if the same day the process started or formatted as MMM_DD (Ex.: Feb_5) if process started the previous day or further in the past.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="tty" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TTY on which the process was started, if applicable.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the effective user id which represents the actual privileges of the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exec_shield" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>A boolean that when true would indicates that ExecShield is enabled for the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="loginuid" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The loginuid shows which account a user gained access to the system with. The /proc/XXXX/loginuid shows this value.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="posix_capability" type="unix-sc:EntityItemCapabilityType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>An effective capability associated with the process. See linux/include/linux/capability.h for more information.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="selinux_domain_label" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>An selinux domain label associated with the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="session_id" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The session ID of the process.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================== ROUTING TABLE ITEM ========================== --> <!-- =============================================================================== --> <xsd:element name="routingtable_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The routingtable_item holds information about an individual routing table entry found in a system's primary routing table. Each routingtable_item contains a destination IP address, gateway, netmask, flags, and the name of the interface associated with it. It is important to note that only numerical addresses will be collected and that their symbolic representations will not be resolved. This equivalent to using the '-n' option with route(8) or netstat(8). It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="destination" type="oval-sc:EntityItemIPAddressType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The destination IP address prefix of the routing table entry. This is the destination IP address and netmask/prefix-length expressed using CIDR notation.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="gateway" type="oval-sc:EntityItemIPAddressType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The gateway of the specified routing table entry.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="flags" type="unix-sc:EntityItemRoutingTableFlagsType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The flags associated with the specified routing table entry.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="interface_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of the interface associated with the routing table entry.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================== RUNLEVEL ITEM =============================== --> <!-- =============================================================================== --> <xsd:element name="runlevel_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The runlevel item holds information about the start or kill state of a specified service at a given runlevel. Each runlevel item contains service_name and runlevel information as well as start and kill information. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="service_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The service_name entity is the actual name of the specific service.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="runlevel" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The runlevel entity specifies is the runlevel the system is currently at.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="start" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The start entity specifies whether the service is scheduled to start at the current runlevel.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="kill" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The kill entity specifies whether the service is scheduled to be killed at the current runlevel.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ================================= SCCS ITEM ================================= --> <!-- =============================================================================== --> <xsd:element name="sccs_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Specifies the absolute path to an SCCS file. A directory cannot be specified as a filepath.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="path" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The path element specifies the directory component of the absolute path to an SCCS file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="filename" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of an SCCS file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="module_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="module_type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="release" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="level" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="branch" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="sequence" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="what_string" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================= SHADOW ITEM =================================== --> <!-- =============================================================================== --> <xsd:element name="shadow_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>/etc/shadow. See shadow(4).</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="username" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the user for which data was gathered.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="password" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the encrypted version of the user's password.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="chg_lst" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the date of the last password change in days since 1/1/1970.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="chg_allow" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This specifies how often in days a user may change their password. It can also be thought of as the minimum age of a password.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="chg_req" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This describes how long a user can keep a password before the system forces her to change it.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exp_warn" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This describes how long before password expiration the system begins warning the user. The system will warn the user at each login.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exp_inact" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This describes how many days of account inactivity the system will wait after a password expires before locking the account? This window, usually only set to a few days, gives users who are logging in very seldomly a bit of extra time to receive the password expiration warning and change their password.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="exp_date" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This specifies when will the account's password expire, in days since 1/1/1970.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="flag" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is a reserved field that the shadow file may use in the future.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="encrypt_method" type="unix-sc:EntityItemEncryptMethodType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The encrypt_method entity describes method that is used for hashing passwords.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================== SYSCTL ITEM ================================= --> <!-- =============================================================================== --> <xsd:element name="sysctl_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The sysctl_item stores information retrieved from the local system about a kernel parameter and its respective value(s).</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name element contains a string that represents the name of a kernel parameter that was collected from the local system.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="value" type="oval-sc:EntityItemAnySimpleType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The value element contains a string that represents the current value(s) for the specified kernel parameter on the local system.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================= UNAME ITEM ==================================== --> <!-- =============================================================================== --> <xsd:element name="uname_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>Information about the hardware the machine is running on. This information is the parsed equivalent of uname -a.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="machine_class" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the machine hardware name. This corresponds to the command uname -m.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="node_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the host name. This corresponds to the command uname -n.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="os_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the operating system name. This corresponds to the command uname -s.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="os_release" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the build version. This corresponds to the command uname -r.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="os_version" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the operating system version. This corresponds to the command uname -v.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="processor_type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This entity specifies the processor type. This corresponds to the command uname -p.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ================================ XINETD ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="xinetd_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The xinetd item holds information associated with different Internet services. It extends the standard ItemType as defined in the oval-system-characteristics schema and one should refer to the ItemType description for more information.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="protocol" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The protocol entity describes the protocol related to the service item.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="service_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The service_name entity describes the name of the service.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="flags" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The flags entity describes miscellaneous settings like TCP keepalives or libwrap deactivation.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="no_access" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="only_from" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The only_from entity describes specifies an exclusive set of IP addresses that may connect to this service</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="port" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="server" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>what program listens on this port</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="server_arguments" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="socket_type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="type" type="unix-sc:EntityItemXinetdTypeStatusType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:element> <xsd:element name="user" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The user entity describes user that xinetd should run the service as.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="wait" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The wait entity describes whether the service allows only one connection at a time.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="disabled" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The disabled entity describes whether this service is on or not.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================================================================== --> <!-- =============================================================================== --> <xsd:complexType name="EntityItemCapabilityType"> <xsd:annotation> <xsd:documentation>The EntityItemCapabilityType complex type restricts a string value to a specific set of values that describe POSIX capability types associated with a process service. This list is based off the values defined in linux/include/linux/capability.h. Documentation on each allowed value can be found in capability.h. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="CAP_CHOWN"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_DAC_OVERRIDE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_DAC_READ_SEARCH"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_FOWNER"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_FSETID"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_KILL"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SETGID"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SETUID"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SETPCAP"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_LINUX_IMMUTABLE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_NET_BIND_SERVICE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_NET_BROADCAST"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_NET_ADMIN"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_NET_RAW"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_IPC_LOCK"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_IPC_OWNER"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_MODULE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_RAWIO"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_CHROOT"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_PTRACE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_ADMIN"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_BOOT"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_NICE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_RESOURCE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_TIME"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SYS_TTY_CONFIG"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_MKNOD"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_LEASE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_AUDIT_WRITE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_AUDIT_CONTROL"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_SETFCAP"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_MAC_OVERRIDE"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CAP_MAC_ADMIN"> <xsd:annotation> <xsd:documentation></xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for empty elements associated with variable references.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemEndpointType"> <xsd:annotation> <xsd:documentation>The EntityItemEndpointType complex type restricts a string value to a specific set of values that describe endpoint types associated with an Internet service. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="stream"> <xsd:annotation> <xsd:documentation>The stream value is used to describe a stream socket.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="dgram"> <xsd:annotation> <xsd:documentation>The dgram value is used to describe a datagram socket.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="raw"> <xsd:annotation> <xsd:documentation>The raw value is used to describe a raw socket.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="seqpacket"> <xsd:annotation> <xsd:documentation>The seqpacket value is used to describe a sequenced packet socket.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="tli"> <xsd:annotation> <xsd:documentation>The tli value is used to describe all TLI endpoints.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemGconfTypeType"> <xsd:annotation> <xsd:documentation>The EntityItemGconfTypeType complex type restricts a string value to the seven values GCONF_VALUE_STRING, GCONF_VALUE_INT, GCONF_VALUE_FLOAT, GCONF_VALUE_BOOL, GCONF_VALUE_SCHEMA, GCONF_VALUE_LIST, and GCONF_VALUE_PAIR that specify the type of the value associated with a GConf preference key. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="GCONF_VALUE_STRING"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_STRING type is used to describe a preference key that has a string value.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_INT"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_INT type is used to describe a preference key that has a integer value.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_FLOAT"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_FLOAT type is used to describe a preference key that has a float value.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_BOOL"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_BOOL type is used to describe a preference key that has a boolean value.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_SCHEMA"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_SCHEMA type is used to describe a preference key that has a schema value. The actual value will be the default value as specified in the GConf schema.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_LIST"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_LIST type is used to describe a preference key that has a list of values. The actual values will be one of the primitive GConf datatypes GCONF_VALUE_STRING, GCONF_VALUE_INT, GCONF_VALUE_FLOAT, GCONF_VALUE_BOOL, and GCONF_VALUE_SCHEMA. Note that all of the values associated with a GCONF_VALUE_LIST are required to have the same type.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GCONF_VALUE_PAIR"> <xsd:annotation> <xsd:documentation>The GCONF_VALUE_PAIR type is used to describe a preference key that has a pair of values. The actual values will consist of the primitive GConf datatypes GCONF_VALUE_STRING, GCONF_VALUE_INT, GCONF_VALUE_FLOAT, GCONF_VALUE_BOOL, and GCONF_VALUE_SCHEMA. Note that the values associated with a GCONF_VALUE_PAIR are not required to have the same type.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemRoutingTableFlagsType"> <xsd:annotation> <xsd:documentation>The EntityItemRoutingTableFlagsType complex type restricts a string value to a specific set of values that describe the flags associated with a routing table entry. This list is based off the values defined in the man pages of various platforms. For Linux, please see route(8). For Solaris, please see netstat(1M). For HP-UX, please see netstat(1). For Mac OS, please see netstat(1). For FreeBSD, please see netstat(1). Documentation on each allowed value can be found in the previously listed man pages. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> <xsd:appinfo> <evaluation_documentation>The following table is a mapping between the generic flag enumeration values and the actual flag values found on the various platforms. If the flag value is not specified, for a particular generic flag enumeration value, the flag value is not defined for that platform.</evaluation_documentation> <evaluation_chart xml:space="preserve"> Name Linux Solaris HPUX Mac OS FreeBSD UP U U U U U GATEWAY G G G G G HOST H H H H H REINSTATE R DYNAMIC D D D D MODIFIED M M M ADDRCONF A A CACHE C REJECT ! R R REDUNDANT M SETSRC S BROADCAST B b b LOCAL L PROTOCOL_1 1 1 PROTOCOL_2 2 2 PROTOCOL_3 3 3 BLACK_HOLE B B CLONING C C PROTOCOL_CLONING c c INTERFACE_SCOPE I LINK_LAYER L L MULTICAST m STATIC S S WAS_CLONED W W XRESOLVE X X </evaluation_chart> </xsd:appinfo> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="UP"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="GATEWAY"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="HOST"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="REINSTATE"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="DYNAMIC"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="MODIFIED"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ADDRCONF"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CACHE"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="REJECT"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="REDUNDANT"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="SETSRC"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="BROADCAST"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="LOCAL"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="PROTOCOL_1"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="PROTOCOL_2"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="PROTOCOL_3"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="BLACK_HOLE"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="CLONING"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="PROTOCOL_CLONING"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="INTERFACE_SCOPE"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="LINK_LAYER"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="MULTICAST"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="STATIC"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="WAS_CLONED"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="XRESOLVE"> <xsd:annotation> <xsd:documentation/> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemXinetdTypeStatusType"> <xsd:annotation> <xsd:documentation>The EntityItemXinetdTypeStatusType complex type restricts a string value to five values, either RPC, INTERNAL, UNLISTED, TCPMUX, or TCPMUXPLUS that specify the type of service registered in xinetd. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="INTERNAL"> <xsd:annotation> <xsd:documentation>The INTERNAL type is used to describe services like echo, chargen, and others whose functionality is supplied by xinetd itself.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="RPC"> <xsd:annotation> <xsd:documentation>The RPC type is used to describe services that use remote procedure call ala NFS.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="UNLISTED"> <xsd:annotation> <xsd:documentation>The UNLISTED type is used to describe services that aren't listed in /etc/protocols or /etc/rpc.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="TCPMUX"> <xsd:annotation> <xsd:documentation>The TCPMUX type is used to describe services that conform to RFC 1078. This type indiciates that the service is responsible for handling the protocol handshake.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="TCPMUXPLUS"> <xsd:annotation> <xsd:documentation>The TCPMUXPLUS type is used to describe services that conform to RFC 1078. This type indicates that xinetd is responsible for handling the protocol handshake.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemWaitStatusType"> <xsd:annotation> <xsd:documentation>The EntityItemWaitStatusType complex type restricts a string value to two values, either wait or nowait, that specify whether the server that is invoked by inetd will take over the listening socket associated with the service, and whether once launched, inetd will wait for that server to exit, if ever, before it resumes listening for new service requests. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="wait"> <xsd:annotation> <xsd:documentation>The value of 'wait' specifies that the server that is invoked by inetd will take over the listening socket associated with the service, and once launched, inetd will wait for that server to exit, if ever, before it resumes listening for new service requests.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="nowait"> <xsd:annotation> <xsd:documentation>The value of 'nowait' specifies that the server that is invoked by inetd will not wait for any existing server to finish before taking over the listening socket associated with the service.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemEncryptMethodType"> <xsd:annotation> <xsd:documentation>The EntityItemEncryptMethodType complex type restricts a string value to a set that corresponds to the allowed encrypt methods used for protected passwords in a shadow file. The empty string is also allowed to support empty elements associated with error conditions.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="DES"> <xsd:annotation> <xsd:documentation>The DES method corresponds to the (none) prefix.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="BSDi"> <xsd:annotation> <xsd:documentation>The BSDi method corresponds to BSDi modified DES or the '_' prefix. </xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="MD5"> <xsd:annotation> <xsd:documentation>The MD5 method corresponds to MD5 for Linux/BSD or the $1$ prefix.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="Blowfish"> <xsd:annotation> <xsd:documentation>The Blowfish method corresponds to Blowfish (OpenBSD) or the $2$ or $2a$ prefixes.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="Sun MD5"> <xsd:annotation> <xsd:documentation>The Sun MD5 method corresponds to the $md5$ prefix.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="SHA-256"> <xsd:annotation> <xsd:documentation>The SHA-256 method corresponds to the $5$ prefix.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="SHA-512"> <xsd:annotation> <xsd:documentation>The SHA-512 method corresponds to the $6$ prefix.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for empty elements associated with variable references.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> <xsd:complexType name="EntityItemInterfaceType"> <xsd:annotation> <xsd:documentation>The EntityItemInterfaceType complex type restricts a string value to a specific set of values. These values describe the different interface types which are defined in 'if_arp.h'. The empty string is also allowed to support empty element associated with variable references. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.</xsd:documentation> </xsd:annotation> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemStringType"> <xsd:enumeration value="ARPHRD_ETHER"> <xsd:annotation> <xsd:documentation>The ARPHRD_ETHER type is used to describe ethernet interfaces.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_FDDI"> <xsd:annotation> <xsd:documentation>The ARPHRD_FDDI type is used to describe fiber distributed data interfaces (FDDI).</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_LOOPBACK"> <xsd:annotation> <xsd:documentation>The ARPHRD_LOOPBACK type is used to describe loopback interfaces.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_VOID"> <xsd:annotation> <xsd:documentation>The ARPHRD_VOID type is used to describe unknown interfaces.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_PPP"> <xsd:annotation> <xsd:documentation>The ARPHRD_PPP type is used to describe point-to-point protocol interfaces (PPP).</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_SLIP"> <xsd:annotation> <xsd:documentation>The ARPHRD_SLIP type is used to describe serial line internet protocol interfaces (SLIP).</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ARPHRD_PRONET"> <xsd:annotation> <xsd:documentation>The ARPHRD_PRONET type is used to describe PROnet token ring interfaces.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value=""> <xsd:annotation> <xsd:documentation>The empty string value is permitted here to allow for detailed error reporting.</xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:schema>
Close
