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.11 /
[ HOME SHELL ]
Name
Size
Permission
Action
aix-definitions-schema.xsd
52.12
KB
-rw-r--r--
aix-system-characteristics-sch...
24.24
KB
-rw-r--r--
android-definitions-schema.xsd
99.3
KB
-rw-r--r--
android-system-characteristics...
58.82
KB
-rw-r--r--
apache-definitions-schema.xsd
13.31
KB
-rw-r--r--
apache-system-characteristics-...
5.7
KB
-rw-r--r--
apple-ios-definitions-schema.x...
39.87
KB
-rw-r--r--
apple-ios-system-characteristi...
29.22
KB
-rw-r--r--
asa-definitions-schema.xsd
119.2
KB
-rw-r--r--
asa-system-characteristics-sch...
55.82
KB
-rw-r--r--
catos-definitions-schema.xsd
37.94
KB
-rw-r--r--
catos-system-characteristics-s...
15.92
KB
-rw-r--r--
esx-definitions-schema.xsd
51.7
KB
-rw-r--r--
esx-system-characteristics-sch...
20.37
KB
-rw-r--r--
freebsd-definitions-schema.xsd
13.63
KB
-rw-r--r--
freebsd-system-characteristics...
7.02
KB
-rw-r--r--
hpux-definitions-schema.xsd
66.97
KB
-rw-r--r--
hpux-system-characteristics-sc...
19.47
KB
-rw-r--r--
independent-definitions-schema...
250.86
KB
-rw-r--r--
independent-system-characteris...
86.93
KB
-rw-r--r--
ios-definitions-schema.xsd
183.57
KB
-rw-r--r--
ios-system-characteristics-sch...
78.97
KB
-rw-r--r--
iosxe-definitions-schema.xsd
135.61
KB
-rw-r--r--
iosxe-system-characteristics-s...
62.13
KB
-rw-r--r--
junos-definitions-schema.xsd
35.04
KB
-rw-r--r--
junos-system-characteristics-s...
14.05
KB
-rw-r--r--
linux-definitions-schema.xsd
226.33
KB
-rw-r--r--
linux-system-characteristics-s...
104.75
KB
-rw-r--r--
macos-definitions-schema.xsd
227.51
KB
-rw-r--r--
macos-system-characteristics-s...
90.36
KB
-rw-r--r--
netconf-definitions-schema.xsd
11.07
KB
-rw-r--r--
netconf-system-characteristics...
3.93
KB
-rw-r--r--
oval-common-schema.xsd
74.93
KB
-rw-r--r--
oval-definitions-schema.xsd
175.93
KB
-rw-r--r--
oval-definitions-schematron.xs...
646.85
KB
-rw-r--r--
oval-directives-schema.xsd
7.56
KB
-rw-r--r--
oval-directives-schematron.xsl
69.75
KB
-rw-r--r--
oval-results-schema.xsd
70.5
KB
-rw-r--r--
oval-results-schematron.xsl
69.69
KB
-rw-r--r--
oval-system-characteristic-sch...
36.56
KB
-rw-r--r--
oval-system-characteristics-sc...
56.49
KB
-rw-r--r--
oval-variables-schema.xsd
7.47
KB
-rw-r--r--
oval-variables-schematron.xsl
6.62
KB
-rw-r--r--
pixos-definitions-schema.xsd
17.41
KB
-rw-r--r--
pixos-system-characteristics-s...
6.9
KB
-rw-r--r--
sharepoint-definitions-schema....
197.36
KB
-rw-r--r--
sharepoint-system-characterist...
93.89
KB
-rw-r--r--
solaris-definitions-schema.xsd
175.55
KB
-rw-r--r--
solaris-system-characteristics...
68.64
KB
-rw-r--r--
unix-definitions-schema.xsd
269.79
KB
-rw-r--r--
unix-system-characteristics-sc...
123.24
KB
-rw-r--r--
windows-definitions-schema.xsd
1.02
MB
-rw-r--r--
windows-system-characteristics...
456.07
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : linux-system-characteristics-schema.xsd
<?xml version="1.0" encoding="utf-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:oval-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" xmlns:linux-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#linux" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#linux" elementFormDefault="qualified" version="5.11"> <xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" schemaLocation="oval-system-characteristics-schema.xsd"/> <xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-common-5" schemaLocation="oval-common-schema.xsd"/> <xsd:annotation> <xsd:documentation>The following is a description of the elements, types, and attributes that compose the Linux 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>Linux System Characteristics</schema> <version>5.11:5.11</version> <date>12/18/2014 09:00:00 AM</date> <terms_of_use>Copyright (c) 2002-2014, 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="linux-sc" uri="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#linux"/> <sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/> </xsd:appinfo> </xsd:annotation> <!-- =============================================================================== --> <!-- ============================== DPKG INFO ITEM =============================== --> <!-- =============================================================================== --> <xsd:element name="dpkginfo_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores DPKG package info.</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>This is the pakage name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="arch" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the architecture for which the DPKG was built, like : i386, ppc, sparc, noarch.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="epoch" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number of the DPKG. For a null epoch (or '(none)' as returned by dpkg) the string '(none)' should be used.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="int"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="release" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the release number of the build.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="version" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the build, changed by the vendor/builder.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="evr" type="oval-sc:EntityItemEVRStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This represents the epoch, version, and release fields as a single version string. It has the form "EPOCH:VERSION-RELEASE". Note that a null epoch (or '(none)' as returned by rpm) is equivalent to '0' and would hence have the form 0:VERSION-RELEASE.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ========================== IF LISTENERS ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="iflisteners_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>An iflisteners_item stores the results of checking for applications that are bound to an interface on the system. Only applications that are bound to an ethernet interface should be collected.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="interface_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the interface (eth0, eth1, fw0, etc.).</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="protocol" type="linux-sc:EntityItemProtocolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the physical layer protocol used by the AF_PACKET socket.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="hw_address" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the hardware address associated with the interface.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="program_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the communicating program.</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. The process in question is that of the program communicating on the network.</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. It represents the owner, and thus privilege level, of the specified program.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ===================== INET LISTENING SERVERS ITEM =========================== --> <!-- =============================================================================== --> <xsd:element name="inetlisteningserver_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>An inet listening server item stores the results of checking for network servers currently active on a system. It holds information pertaining to a specific protocol-address-port combination.</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>This is the transport-layer protocol, in lowercase: tcp or udp.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="local_address" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address associated with the inet listening server. Note that the IP address can be IPv4 or IPv6.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="local_port" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TCP or UDP port on which the program listens.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="local_full_address" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address and network port on which the program listens, equivalent to local_address:local_port. Note that the IP address can be IPv4 or IPv6.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="program_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the communicating program.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="foreign_address" type="oval-sc:EntityItemIPAddressStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address with which the program is communicating, or with which it will communicate, in the case of a listening server. Note that the IP address can be IPv4 or IPv6.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="foreign_port" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TCP or UDP port to which the program communicates. In the case of a listening program accepting new connections, this value will be 0.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="foreign_full_address" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address and network port to which the program is communicating or will accept communications from, equivalent to foreign_address:foreign_port. Note that the IP address can be IPv4 or IPv6.</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. The process in question is that of the program communicating on the network.</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. It represents the owner, and thus privilege level, of the specified program.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================= PARTITION ITEM ================================ --> <!-- =============================================================================== --> <xsd:element name="partition_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>The partition_item stores information about a partition on the local system.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="mount_point" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The mount_point element contains a string that represents the mount point of a partition on the local system.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="device" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The device element contains a string that represents the name of the device.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="uuid" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The uuid element contains a string that represents the universally unique identifier associated with a partition.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="fs_type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The fs_type element contains a string that represents the type of filesystem on a partition.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mount_options" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The mount_options element contains a string that represents a mount option associated with a partition on the local system.</xsd:documentation> <xsd:documentation>Implementation note: not all mount options are visible in /etc/mtab or /proc/mounts. A complete source of additional mount options is the f_flag field of 'struct statvfs'. See statvfs(2). /etc/fstab may have additional mount options, but it need not contain all mounted filesystems, so it MUST NOT be relied upon. Implementers MUST be sure to get all mount options in some way.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="total_space" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The total_space element contains an integer that represents the total number of blocks on a partition.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="space_used" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The space_used element contains an integer that represents the number of blocks used on a partition.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="space_left" type="oval-sc:EntityItemIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The space_left element contains an integer that represents the number of blocks left on a partition.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ============================ RPM INFO ITEM ================================== --> <!-- =============================================================================== --> <xsd:element name="rpminfo_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores rpm info.</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>This is the pakage name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="arch" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the architecture for which the RPM was built, like : i386, ppc, sparc, noarch. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be i686.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="epoch" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number of the RPM, this is used as a kludge for version-release comparisons where the vendor has done some kind of re-numbering or version forking. For a null epoch (or '(none)' as returned by rpm) the string '(none)' should be used. This number is not revealed by a normal query of the RPM's information -- you must use a formatted rpm query command to gather this data from the command line, like so. For an already-installed RPM: rpm -q --qf '%{EPOCH}\n' installed_rpm For an RPM file that has not been installed: rpm -qp --qf '%{EPOCH}\n' rpm_file</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="int"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="release" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the release number of the build.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="version" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the build, changed by the vendor/builder. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="evr" type="oval-sc:EntityItemEVRStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This represents the epoch, version, and release fields as a single version string. It has the form "EPOCH:VERSION-RELEASE". Note that a null epoch (or '(none)' as returned by rpm) is equivalent to '0' and would hence have the form 0:VERSION-RELEASE.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="signature_keyid" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This field contains the PGP key ID that the RPM issuer (generally the original operating system vendor) uses to sign the key. PGP is used to verify the authenticity and integrity of the RPM being considered. Software packages and patches are signed cryptographically to allow administrators to allay concerns that the distribution mechanism has been compromised, whether that mechanism is web site, FTP server, or even a mirror controlled by a hostile party. OVAL uses this field most of all to confirm that the package installed on the system is that shipped by the vendor, since comparing package version numbers against patch announcements is only programmatically valid if the installed package is known to contain the patched code.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="extended_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This represents the name, epoch, version, release, and architecture fields as a single version string. It has the form "NAME-EPOCH:VERSION-RELEASE.ARCHITECTURE". Note that a null epoch (or '(none)' as returned by rpm) is equivalent to '0' and would hence have the form NAME-0:VERSION-RELEASE.ARCHITECTURE.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="filepath" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>This field contains the absolute path of a file or directory included in the rpm.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =========================== RPM VERIFY ITEM ================================= --> <!-- =============================================================================== --> <xsd:element name="rpmverify_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores rpm verification results similar to what is produced by the rpm -V command.</xsd:documentation> <xsd:appinfo> <oval:deprecated_info> <oval:version>5.10</oval:version> <oval:reason>Replaced by the rpmverifyfile_item and rpmverifypackage_item. The rpmverify_item was split into two items to distinguish between the verification of the files in an rpm and the verification of an rpm as a whole. By making this distinction, content authoring is simplified and information is no longer duplicated across items. See the rpmverifyfile_item and rpmverifypackage_item.</oval:reason> <oval:comment>This state has been deprecated and will be removed in version 6.0 of the language.</oval:comment> </oval:deprecated_info> <sch:pattern id="linux-sc_rpmverify_item_dep"> <sch:rule context="linux-sc:rpmverify_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="name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the package name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <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 or directory in the specified package.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="size_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The size_differs entity aligns with the first character ('S' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mode_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The mode_differs entity aligns with the second character ('M' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="md5_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The md5_differs entity aligns with the third character ('5' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="device_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The device_differs entity aligns with the fourth character ('D' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="link_mismatch" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The link_mismatch entity aligns with the fifth character ('L' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ownership_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The ownership_differs entity aligns with the sixth character ('U' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="group_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The group_differs entity aligns with the seventh character ('U' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mtime_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The mtime_differs entity aligns with the eighth character ('T' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="capabilities_differ" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The size_differs entity aligns with the ninth character ('P' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="configuration_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The configuration_file entity represents the configuration file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="documentation_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The documentation_file entity represents the documenation file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ghost_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The ghost_file entity represents the ghost file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="license_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The license_file entity represents the license file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="readme_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The readme_file entity represents the readme file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ========================= RPM VERIFY FILE ITEM ============================== --> <!-- =============================================================================== --> <xsd:element name="rpmverifyfile_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores the verification results of the individual files in an rpm similar to what is produced by the rpm -V command.</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>This is the package name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="epoch" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number of the RPM, this is used as a kludge for version-release comparisons where the vendor has done some kind of re-numbering or version forking. For a null epoch (or '(none)' as returned by rpm) the string '(none)' should be used.. This number is not revealed by a normal query of the RPM's information -- you must use a formatted rpm query command to gather this data from the command line, like so. For an already-installed RPM: rpm -q --qf '%{EPOCH}\n' installed_rpm For an RPM file that has not been installed: rpm -qp --qf '%{EPOCH}\n' rpm_file</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="int"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="version" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the build. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="release" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the release number of the build, changed by the vendor/builder.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="arch" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the architecture for which the RPM was built, like : i386, ppc, sparc, noarch. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be i686.</xsd:documentation> </xsd:annotation> </xsd:element> <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 or directory in the specified package.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="extended_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This represents the name, epoch, version, release, and architecture fields as a single version string. It has the form "NAME-EPOCH:VERSION-RELEASE.ARCHITECTURE". Note that a null epoch (or '(none)' as returned by rpm) is equivalent to '0' and would hence have the form NAME-0:VERSION-RELEASE.ARCHITECTURE.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="size_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The size_differs entity aligns with the first character ('S' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mode_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The mode_differs entity aligns with the second character ('M' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="md5_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The md5_differs entity aligns with the third character ('5' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="device_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The device_differs entity aligns with the fourth character ('D' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="link_mismatch" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The link_mismatch entity aligns with the fifth character ('L' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ownership_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The ownership_differs entity aligns with the sixth character ('U' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="group_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The group_differs entity aligns with the seventh character ('U' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="mtime_differs" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The mtime_differs entity aligns with the eighth character ('T' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="capabilities_differ" type="linux-sc:EntityItemRpmVerifyResultType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The size_differs entity aligns with the ninth character ('P' flag) in the character string in the output generated by running rpm –V on a specific file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="configuration_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The configuration_file entity represents the configuration file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="documentation_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The documentation_file entity represents the documenation file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="ghost_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The ghost_file entity represents the ghost file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="license_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The license_file entity represents the license file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="readme_file" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The readme_file entity represents the readme file attribute marker that may be present on a file.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ======================= RPM VERIFY PACKAGE ITEM ============================= --> <!-- =============================================================================== --> <xsd:element name="rpmverifypackage_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores the rpm verification results of an rpm similar to what is produced by the rpm -V command.</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>This is the package name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="epoch" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number of the RPM, this is used as a kludge for version-release comparisons where the vendor has done some kind of re-numbering or version forking. For a null epoch (or '(none)' as returned by rpm) the string '(none)' should be used.. This number is not revealed by a normal query of the RPM's information -- you must use a formatted rpm query command to gather this data from the command line, like so. For an already-installed RPM: rpm -q --qf '%{EPOCH}\n' installed_rpm For an RPM file that has not been installed: rpm -qp --qf '%{EPOCH}\n' rpm_file</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="int"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="version" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the build. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="release" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the release number of the build, changed by the vendor/builder.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval-sc:EntityItemAnySimpleType"> <xsd:attribute name="datatype" use="optional" default="string"> <xsd:simpleType> <xsd:restriction base="oval:SimpleDatatypeEnumeration"> <xsd:enumeration value="string"/> <xsd:enumeration value="version"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> <xsd:element name="arch" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the architecture for which the RPM was built, like : i386, ppc, sparc, noarch. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be i686.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="extended_name" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This represents the name, epoch, version, release, and architecture fields as a single version string. It has the form "NAME-EPOCH:VERSION-RELEASE.ARCHITECTURE". Note that a null epoch (or '(none)' as returned by rpm) is equivalent to '0' and would hence have the form NAME-0:VERSION-RELEASE.ARCHITECTURE.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="dependency_check_passed" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The dependency_check_passed entity indicates whether or not the dependency check passed. If the dependency check is not performed, due to the 'nodeps' behavior, this entity must not be collected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="digest_check_passed" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The digest_check_passed entity indicates whether or not the verification of the package or header digests passed. If the digest check is not performed, due to the 'nodigest' behavior, this entity must not be collected.</xsd:documentation> <xsd:appinfo> <oval:deprecated_info> <oval:version>5.11</oval:version> <oval:reason>The digest_check_passed item entity can not be collected as implemented, and has become irrelevant.</oval:reason> <oval:comment>This item entity has been deprecated and will be removed in version 6.0 of the language.</oval:comment> </oval:deprecated_info> <sch:pattern id="linux-sc_rpmverifypackage_dicp_dep"> <sch:rule context="linux-sc:rpmverifypackage_item/linux-sc:digest_check_passed"> <sch:report test="true()">DEPRECATED ELEMENT: <sch:value-of select="name()"/> ID: <sch:value-of select="../@id"/></sch:report> </sch:rule> </sch:pattern> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="verification_script_successful" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The verification_script_successful entity indicates whether or not the verification script executed successfully. If the verification script is not executed, due to the 'noscripts' behavior, this entity must not be collected.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="signature_check_passed" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The signature_check_passed entity indicates whether or not the verification of the package or header signatures passed. If the signature check is not performed, due to the 'nosignature' behavior, this entity must not be collected.</xsd:documentation> <xsd:appinfo> <oval:deprecated_info> <oval:version>5.11</oval:version> <oval:reason>The signature_check_passed item entity can not be collected as implemented, and has become irrelevant.</oval:reason> <oval:comment>This item entity has been deprecated and will be removed in version 6.0 of the language.</oval:comment> </oval:deprecated_info> <sch:pattern id="linux-sc_rpmverifypackage_dicp_dep"> <sch:rule context="linux-sc:rpmverifypackage_item/linux-sc:signature_check_passed"> <sch:report test="true()">DEPRECATED ELEMENT: <sch:value-of select="name()"/> ID: <sch:value-of select="../@id"/></sch:report> </sch:rule> </sch:pattern> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =========================== SELINUX BOOLEAN ITEM ============================ --> <!-- =============================================================================== --> <xsd:element name="selinuxboolean_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item describes the current and pending status of a SELinux boolean. 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 of the SELinux boolean.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="current_status" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The current_status entity indicates current state of the specified SELinux boolean.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="pending_status" type="oval-sc:EntityItemBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The pending_status entity indicates the pending state of the specified SELinux boolean.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ====================== SELINUX SECURITY CONTEXT ITEM ======================== --> <!-- =============================================================================== --> <xsd:element name="selinuxsecuritycontext_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item describes the SELinux security context of a file or process on the local system. This item follows the SELinux security context structure: user:role:type:low_sensitivity[:low_category]- high_sensitivity [:high_category]. 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="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="user" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The user element specifies the SELinux user that either created the file or started the process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="role" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The role element specifies the types that a process may transition to (domain transitions). Note that this entity is not relevant for files and will always have a value of object_r.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="type" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The type element specifies the domain in which the file is accessible or the domain in which a process executes.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="low_sensitivity" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The low_sensitivity element specifies the current sensitivity of a file or process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="low_category" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The low_category element specifies the set of categories associated with the low sensitivity.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="high_sensitivity" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The high_sensitivity element specifies the maximum range for a file or the clearance for a process.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="high_category" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The high_category element specifies the set of categories associated with the high sensitivity.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="rawlow_sensitivity" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The rawlow_sensitivity element specifies the current sensitivity of a file or process but in its raw context.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="rawlow_category" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The rawlow_category element specifies the set of categories associated with the low sensitivity but in its raw context.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="rawhigh_sensitivity" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The rawhigh_sensitivity element specifies the maximum range for a file or the clearance for a process but in its raw context.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="rawhigh_category" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The rawhigh_category element specifies the set of categories associated with the high sensitivity but in its raw context.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ========================== SLACKWARE PKG INFO ITEM ========================== --> <!-- =============================================================================== --> <xsd:element name="slackwarepkginfo_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item describes info related to Slackware packages. 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>This is the pakage name to check.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="version" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the pakage.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="architecture" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the architecture the package is designed for.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="revision" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the revision of the package.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ======================= SYSTEMD UNIT DEPENDENCY ITEM ======================== --> <!-- =============================================================================== --> <xsd:element name="systemdunitdependency_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores the dependencies of the systemd unit. Please refer to the individual elements in the schema for more details about what each represents.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="unit" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The unit entity refers to the full systemd unit name, which has a form of "$name.$type". For example "cupsd.service". This name is usually also the filename of the unit configuration file located in the /etc/systemd/ and /usr/lib/systemd/ directories.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="dependency" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>The dependency entity refers to the name of a unit that was confirmed to be a dependency of the given unit.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- ======================= SYSTEMD UNIT PROPERTY ITEM ========================== --> <!-- =============================================================================== --> <xsd:element name="systemdunitproperty_item" substitutionGroup="oval-sc:item"> <xsd:annotation> <xsd:documentation>This item stores the properties and values of a systemd unit.</xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval-sc:ItemType"> <xsd:sequence> <xsd:element name="unit" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The unit entity refers to the full systemd unit name, which has a form of "$name.$type". For example "cupsd.service". This name is usually also the filename of the unit configuration file located in the /etc/systemd/ and /usr/lib/systemd/ directories.</xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="property" type="oval-sc:EntityItemStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of the property associated with a systemd unit.</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 property associated with a systemd unit. Exactly one value shall be used for all property types except dbus arrays - each array element shall be represented by one value.</xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <!-- =============================================================================== --> <!-- =============================================================================== --> <!-- =============================================================================== --> <xsd:complexType name="EntityItemRpmVerifyResultType"> <xsd:annotation> <xsd:documentation>The EntityItemRpmVerifyResultType complex type restricts a string value to the set of possible outcomes of checking an attribute of a file included in an RPM against the actual value of that attribute in the RPM database. 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="pass"> <xsd:annotation> <xsd:documentation>'pass' indicates that the test passed and is equivalent to the '.' value reported by the rpm -V command.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="fail"> <xsd:annotation> <xsd:documentation>'fail' indicates that the test failed and is equivalent to a bold charcter in the test result string reported by the rpm -V command.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="not performed"> <xsd:annotation> <xsd:documentation>'not performed' indicates that the test could not be performed and is equivalent to the '?' value reported by the rpm -V command.</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="EntityItemProtocolType"> <xsd:annotation> <xsd:documentation>The EntityStateProtocolType complex type restricts a string value to the set of physical layer protocols used by AF_PACKET sockets. The empty string is also allowed to support the 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="ETH_P_LOOP"> <xsd:annotation> <xsd:documentation>Ethernet loopback packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PUP"> <xsd:annotation> <xsd:documentation>Xerox PUP packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PUPAT"> <xsd:annotation> <xsd:documentation>Xerox PUP Address Transport packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IP"> <xsd:annotation> <xsd:documentation>Internet protocol packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_X25"> <xsd:annotation> <xsd:documentation>CCITT X.25 packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ARP"> <xsd:annotation> <xsd:documentation>Address resolution packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_BPQ"> <xsd:annotation> <xsd:documentation>G8BPQ AX.25 ethernet packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IEEEPUP"> <xsd:annotation> <xsd:documentation>Xerox IEEE802.3 PUP packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IEEEPUPAT"> <xsd:annotation> <xsd:documentation>Xerox IEEE802.3 PUP address transport packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DEC"> <xsd:annotation> <xsd:documentation>DEC assigned protocol.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DNA_DL"> <xsd:annotation> <xsd:documentation>DEC DNA Dump/Load.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DNA_RC"> <xsd:annotation> <xsd:documentation>DEC DNA Remote Console.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DNA_RT"> <xsd:annotation> <xsd:documentation>DEC DNA Routing.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_LAT"> <xsd:annotation> <xsd:documentation>DEC LAT.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DIAG"> <xsd:annotation> <xsd:documentation>DEC Diagnostics.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_CUST"> <xsd:annotation> <xsd:documentation>DEC Customer use.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_SCA"> <xsd:annotation> <xsd:documentation>DEC Systems Comms Arch.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_RARP"> <xsd:annotation> <xsd:documentation>Reverse address resolution packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ATALK"> <xsd:annotation> <xsd:documentation>Appletalk DDP.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_AARP"> <xsd:annotation> <xsd:documentation>Appletalk AARP.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_8021Q"> <xsd:annotation> <xsd:documentation>802.1Q VLAN Extended Header.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IPX"> <xsd:annotation> <xsd:documentation>IPX over DIX.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IPV6"> <xsd:annotation> <xsd:documentation>IPv6 over bluebook.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_SLOW"> <xsd:annotation> <xsd:documentation>Slow Protocol. See 802.3ad 43B.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_WCCP"> <xsd:annotation> <xsd:documentation>Web-cache coordination protocol.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PPP_DISC"> <xsd:annotation> <xsd:documentation>PPPoE discovery messages.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PPP_SES"> <xsd:annotation> <xsd:documentation>PPPoE session messages.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_MPLS_UC"> <xsd:annotation> <xsd:documentation>MPLS Unicast traffic.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_MPLS_MC"> <xsd:annotation> <xsd:documentation>MPLS Multicast traffic.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ATMMPOA"> <xsd:annotation> <xsd:documentation>MultiProtocol Over ATM.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ATMFATE"> <xsd:annotation> <xsd:documentation>Frame-based ATM Transport over Ethernet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_AOE"> <xsd:annotation> <xsd:documentation>ATA over Ethernet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_TIPC"> <xsd:annotation> <xsd:documentation>TIPC.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_802_3"> <xsd:annotation> <xsd:documentation>Dummy type for 802.3 frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_AX25"> <xsd:annotation> <xsd:documentation>Dummy protocol id for AX.25.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ALL"> <xsd:annotation> <xsd:documentation>Every packet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_802_2"> <xsd:annotation> <xsd:documentation>802.2 frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_SNAP"> <xsd:annotation> <xsd:documentation>Internal only.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_DDCMP"> <xsd:annotation> <xsd:documentation>DEC DDCMP: Internal only</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_WAN_PPP"> <xsd:annotation> <xsd:documentation>Dummy type for WAN PPP frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PPP_MP"> <xsd:annotation> <xsd:documentation>Dummy type for PPP MP frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_PPPTALK"> <xsd:annotation> <xsd:documentation>Dummy type for Atalk over PPP.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_LOCALTALK"> <xsd:annotation> <xsd:documentation>Localtalk pseudo type.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_TR_802_2"> <xsd:annotation> <xsd:documentation>802.2 frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_MOBITEX"> <xsd:annotation> <xsd:documentation>Mobitex.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_CONTROL"> <xsd:annotation> <xsd:documentation>Card specific control frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_IRDA"> <xsd:annotation> <xsd:documentation>Linux-IrDA.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ECONET"> <xsd:annotation> <xsd:documentation>Acorn Econet.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_HDLC"> <xsd:annotation> <xsd:documentation>HDLC frames.</xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="ETH_P_ARCNET"> <xsd:annotation> <xsd:documentation>1A for ArcNet.</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
