Docs for schema redhat-oval-results-schema.xsd in Open Vulnerability and Assessment Language (OVAL®)

This document outlines the Red Hat Linux specific tests of the OVAL Results XML schema. Each test is an extention of a basic OVAL test defined in the default OVAL Results XML schema. 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:schema targetNamespace="http://oval.mitre.org/XMLSchema/oval_results#redhat" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval_results="http://oval.mitre.org/XMLSchema/oval_results" xmlns:redhat="http://oval.mitre.org/XMLSchema/oval_results#redhat" elementFormDefault="qualified" version="4.2"> <xsd:import namespace="http://oval.mitre.org/XMLSchema/oval_results" schemaLocation="oval-results-schema.xsd"/> <xsd:annotation> <xsd:documentation>This document outlines the Red Hat Linux specific tests of the OVAL Results XML schema. Each test is an extention of a basic OVAL test defined in the default OVAL Results XML schema.</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>Red Hat Results</schema> <version>4.2</version> <date>2 December 2005</date> </xsd:appinfo> </xsd:annotation>    <xsd:element name="file_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the file_test found in the unix-oval-results-schema.</xsd:documentation> <xsd:documentation>This test checks file metadata.</xsd:documentation> <xsd:appinfo> <test_name>File Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="path" type="redhat:componentType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Specifies the absolute path to a file on the machine. This path can be created from multiple components that are added together. When a pattern match operator is used, the corresponding regular expression is matched against the set of absolute path strings. These string would not include the '.' and '..' notations. This means that a '.*' component of a regular expression will not only match all files in the specified directories, but all subdirectories, their subdirectories, etc.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>1</cardinality> <content>none</content> <valid_datatypes>component</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="type" type="oval_results:subtestStringType" 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:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="group_id" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the group owner of the file, by group number.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval_results:subtestStringType" 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:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="a_time" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of the last access, in seconds since the last epoch.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="c_time" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of the last change to the file's inode, which stores all.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="m_time" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of the last change to the file's contents.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="md5" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the MD5 hash of the file's contents, which serves as a kind of content integrity check.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="path" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The absolute path string of a matching file object.</xsd:documentation> <xsd:appinfo> <parent_test>File Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="inetlisteningservers_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>An inet listening server test checks for network servers currently active on a system.</xsd:documentation> <xsd:appinfo> <test_name>Inet Listening Servers Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="program_name" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the communicating program.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="local_address" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address of the network interface on which the program listens.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="local_full_address" type="oval_results:subtestStringType" 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.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="local_port" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TCP or UDP port on which the program listens. Note that this is not a list -- if a program listens on multiple ports, or on a combination of TCP and UDP, each will have its own entry in the table data stored by this test.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="foreign_address" type="oval_results:subtestStringType" 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.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="foreign_full_address" type="oval_results:subtestStringType" 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.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="foreign_port" type="oval_results:subtestStringType" 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 is usually a *.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="pid" type="oval_results:subtestIntType" 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:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>integer</content> <valid_datatypes>integer</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="protocol" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the transport-layer protocol, in lowercase: tcp or udp.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="program_name" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of a matching communicating program.</xsd:documentation> <xsd:appinfo> <parent_test>Inet Listening Servers Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="interface_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the interface_test found in the unix-oval-results-schema.</xsd:documentation> <xsd:documentation>Enumerate various attributes about the interfaces on a system.</xsd:documentation> <xsd:appinfo> <test_name>Interface Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the interface (eth0, eth1, etc.) name to check.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="hardware_addr" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the hardware or MAC address of the physical network card.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="inet_addr" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the IP address of the interface.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="broadcast_addr" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the broadcast IP address for this interface's network, like 192.168.255.255.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="netmask" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the bitmask used to calculate the inteface'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.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="flag" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Interface Test</parent_test> <cardinality>0-n</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of a matching interface object.</xsd:documentation> <xsd:appinfo> <parent_test>Interface Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="permission_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the permission_test found in the unix-oval-results-schema.</xsd:documentation> <xsd:documentation>A permission test checks to see if a file has a specified permission.</xsd:documentation> <xsd:appinfo> <test_name>Permission Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="path" type="redhat:componentType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Specifies the absolute path to a file on the machine. This path can be created from multiple components that are added together. When a pattern match operator is used, the corresponding regular expression is matched against the set of absolute path strings. These string would not include the '.' and '..' notations. This means that a '.*' component of a regular expression will not only match all files in the specified directories, but all subdirectories, their subdirectories, etc.</xsd:documentation> <xsd:appinfo> <parent_test>Permission Test</parent_test> <cardinality>1</cardinality> <content>none</content> <valid_datatypes>component</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="gexec" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="gread" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="gwrite" type="oval_results:subtestBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the group owner of the file write to this file or directory?</xsd:documentation> <xsd:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="oexec" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="oread" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="owrite" type="oval_results:subtestBoolType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Can the other users write to this file or directory?</xsd:documentation> <xsd:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="sgid" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="sticky" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="suid" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="uexec" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="uread" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="uwrite" type="oval_results:subtestBoolType" 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:appinfo> <parent_test>Permission Test</parent_test> <cardinality>0-1</cardinality> <content>boolean</content> <valid_datatypes>boolean</valid_datatypes> <valid_operators>equals, not equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="path" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The absolute path string of a matching file object.</xsd:documentation> <xsd:appinfo> <parent_test>Permission Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="process_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the process_test found in the unix-oval-results-schema.</xsd:documentation> <xsd:documentation>Output of /usr/bin/ps -ecf. See ps(1).</xsd:documentation> <xsd:appinfo> <test_name>Process Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="command" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This specifies the command/program name to check.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="exec_time" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the amount of CPU time (not clock time) that the process has consumed, formatted in HH:MM:SS or days.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="pid" type="oval_results:subtestIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>integer</content> <valid_datatypes>integer</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="ppid" type="oval_results:subtestIntType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the process ID of the process's parent process.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>integer</content> <valid_datatypes>integer</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="priority" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="scheduling_class" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>A characteristic maintained by the scheduler: RT (real-time), TS (timeshare), B (batch), BC (batch critical), WL (weightless) and GN (gang scheduled).</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="start_time" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the time of day in which the process was started in either HH:MM:SS or days.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tty" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the TTY on which the process was started, if applicable.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="user_id" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Process Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="command" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The name of a matching command/program.</xsd:documentation> <xsd:appinfo> <parent_test>Process Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="rpminfo_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test checks rpm info.</xsd:documentation> <xsd:appinfo> <test_name>RPM Info Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the package name to check.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="arch" type="oval_results:subtestStringType" 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:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="epoch" type="oval_results:subtestStringType" 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. 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:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="release" type="oval_results:subtestStringType" 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 21.11.4.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="version" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the software built in this RPM. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40. This is the version number assigned by the apache code maintainers.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="evr_version" type="oval_results:subtestStringType" 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".</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, greater than, less than, greater than or equal, less than or equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="signature_keyid" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This field is used to see if the RMP has been signed by the expected party.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of a matching package object.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Info Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="rpmversioncompare_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the rpminfo_test.</xsd:documentation> <xsd:documentation>This test compares rpm version info.</xsd:documentation> <xsd:appinfo> <test_name>RPM Version Compare Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the package name to check.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_epoch" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number to test against. The epoch is used as a kludge for version-release comparisons where the vendor has done some kind of re-numbering or version forking. 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:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_version" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the software that we want to test against. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40. This is the version number assigned by the apache code maintainers.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_release" type="oval_results:subtestStringType" minOccurs="1" 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 21.11.4.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="installed_version" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the result of the comparison: earlier, equal, later or not installed.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:restriction base="oval_results:subtestStringType"> <xsd:enumeration value="earlier"/> <xsd:enumeration value="equal"/> <xsd:enumeration value="later"/> <xsd:enumeration value=""/> </xsd:restriction> </xsd:simpleContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="name" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of a matching package object.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_epoch" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the epoch number to test against. The epoch is used as a kludge for version-release comparisons where the vendor has done some kind of re-numbering or version forking. 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:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_version" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the version number of the software that we want to test against. In the case of an apache rpm named httpd-2.0.40-21.11.4.i686.rpm, this value would be 2.0.40. This is the version number assigned by the apache code maintainers.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="tested_release" type="oval_results:testedStringType" minOccurs="1" 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 21.11.4.</xsd:documentation> <xsd:appinfo> <parent_test>RPM Version Compare Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="shadow_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>/etc/shadow. See shadow(4).</xsd:documentation> <xsd:appinfo> <test_name>Shadow Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="username" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of the user being checked.</xsd:documentation> <xsd:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="password" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the encrypted version of the user's password.</xsd:documentation> <xsd:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="chg_lst" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="chg_allow" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="chg_req" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="exp_warn" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="exp_inact" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="exp_date" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This speicifies when will the account's password expire, in days since 1/1/1970.</xsd:documentation> <xsd:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="flag" type="oval_results:subtestStringType" 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:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="username" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the name of a matching user.</xsd:documentation> <xsd:appinfo> <parent_test>Shadow Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="textfilecontent_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the textfilecontent_test found in the independent-schema.</xsd:documentation> <xsd:documentation>This test checks the contents of a text file.</xsd:documentation> <xsd:appinfo> <test_name>Text File Content Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="path" type="redhat:componentType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Specifies the absolute path to a file on the machine. This path can be created from multiple components that are added together. When a pattern match operator is used, the corresponding regular expression is matched against the set of absolute path strings. These string would not include the '.' and '..' notations. This means that a '.*' component of a regular expression will not only match all files in the specified directories, but all subdirectories, their subdirectories, etc.</xsd:documentation> <xsd:appinfo> <parent_test>Text File Content Test</parent_test> <cardinality>1</cardinality> <content>none</content> <valid_datatypes>component</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="line" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>The line element represents a line in the file and is represented using a regular expression.</xsd:documentation> <xsd:appinfo> <parent_test>Text File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="subexpression" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="unbounded"> <xsd:annotation> <xsd:documentation>Each subexpression in the regular expression of the line element is then tested against the value specified in the subexpression element.</xsd:documentation> <xsd:appinfo> <parent_test>Text File Content Test</parent_test> <cardinality>0-n</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="path" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The absolute path string of a matching text file object.</xsd:documentation> <xsd:appinfo> <parent_test>Text File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="line" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>The line element represents a line in the file and is represented using a regular expression.</xsd:documentation> <xsd:appinfo> <parent_test>Text File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="uname_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the uname_test found in the unix-oval-results-schema.</xsd:documentation> <xsd:documentation>uname -a command output.</xsd:documentation> <xsd:appinfo> <test_name>Uname Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_data" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="machine_class" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the machine hardware name, 5th field from uname -a.</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="node_name" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the host name, the 2nd field from uname -a.</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="os_name" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the operating system name, the 1st field from uname -a.</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="os_release" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the build version, 4th field from uname -a. For example, from a running Linux system: "#1 Wed Aug 25 13:34:40 UTC 2004"</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="os_version" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the operating system version, the 3rd field from uname -a.</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="processor_type" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>This is the processor type, 6th field from uname -a.</xsd:documentation> <xsd:appinfo> <parent_test>Uname Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" type="oval_results:testedObjectType" minOccurs="0" maxOccurs="1"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:element name="xmlfilecontent_test" substitutionGroup="oval_results:test"> <xsd:annotation> <xsd:documentation>This test has been deprecated in version 4.1 of the redhat-oval-results-schema and will be removed completely in version 5. It is recommended that all future OVAL Content use the xmlfilecontent_test found in the independent-oval-results-schema.</xsd:documentation> <xsd:documentation>This test checks the contents of an xml file.</xsd:documentation> <xsd:appinfo> <test_name>XML File Content Test</test_name> <extends>standardTestType</extends> <valid_sections>message, definition_object, definition_data, tested_object</valid_sections> <example></example> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:standardTestType"> <xsd:sequence> <xsd:element name="definition_object" minOccurs="1" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionObjectType"> <xsd:sequence> <xsd:element name="path" type="redhat:componentType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>Specifies the absolute path to a file on the machine. This path can be created from multiple components that are added together. When a pattern match operator is used, the corresponding regular expression is matched against the set of absolute path strings. These string would not include the '.' and '..' notations. This means that a '.*' component of a regular expression will not only match all files in the specified directories, but all subdirectories, their subdirectories, etc.</xsd:documentation> <xsd:appinfo> <parent_test>XML File Content Test</parent_test> <cardinality>1</cardinality> <content>none</content> <valid_datatypes>component</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="xpath" type="oval_results:subtestStringType" minOccurs="1" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>Specifies an Xpath expression describing the nodes to look at.</xsd:documentation> <xsd:appinfo> <parent_test>XML File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="definition_data" minOccurs="0" maxOccurs="1"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:definitionDataType"> <xsd:sequence> <xsd:element name="value_of" type="oval_results:subtestStringType" minOccurs="0" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The value element checks the value of the nodes found. How this is used is entirely controlled by operator attributes.</xsd:documentation> <xsd:appinfo> <parent_test>XML File Content Test</parent_test> <cardinality>0-1</cardinality> <content>string</content> <valid_datatypes>string</valid_datatypes> <valid_operators>equals, not equal, pattern match</valid_operators> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> <xsd:element name="tested_object" minOccurs="0" maxOccurs="unbounded"> <xsd:complexType> <xsd:complexContent> <xsd:extension base="oval_results:testedObjectType"> <xsd:sequence> <xsd:element name="path" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1"> <xsd:annotation> <xsd:documentation>The absolute path string of a matching XML file object.</xsd:documentation> <xsd:appinfo> <parent_test>XML File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> <xsd:element name="xpath" type="oval_results:testedStringType" minOccurs="1" maxOccurs="1" nillable="true"> <xsd:annotation> <xsd:documentation>Specifies an Xpath expression describing the nodes to look at.</xsd:documentation> <xsd:appinfo> <parent_test>XML File Content Test</parent_test> <cardinality>1</cardinality> <content>string</content> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:element>    <xsd:complexType name="componentType"> <xsd:annotation> <xsd:documentation>The component type allows a value to obtained by combining different pieces from other sources. Each component element has an attribute called type. The value of this attribute determines where to get the string used to build the file path. A type of literal means: use the value of the component element as is.</xsd:documentation> </xsd:annotation> <xsd:complexContent> <xsd:extension base="oval_results:subtestBaseType"> <xsd:sequence> <xsd:element name="component" minOccurs="1" maxOccurs="unbounded"> <xsd:complexType> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="type" use="required"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="literal"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType> </xsd:element> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType>    <xsd:element name="platform" substitutionGroup="oval_results:platformBase"> <xsd:annotation> <xsd:documentation>The valid platforms for the RedHat Linux family.</xsd:documentation> </xsd:annotation> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="Red Hat Linux 9"/> <xsd:enumeration value="Red Hat Enterprise Linux 3"/> <xsd:enumeration value="Red Hat Enterprise Linux 4"/> </xsd:restriction> </xsd:simpleType> </xsd:element> </xsd:schema>

Schema Name:	redhat-oval-results-schema.xsd
Target Namespace:	http://oval.mitre.org/XMLSchema/oval_results#redhat
Documentation:	This document outlines the Red Hat Linux specific tests of the OVAL Results XML schema. Each test is an extention of a basic OVAL test defined in the default OVAL Results XML schema. 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.

Elements:
	file_test inetlisteningservers_test interface_test permission_test platform process_test rpminfo_test rpmversioncompare_test shadow_test textfilecontent_test uname_test xmlfilecontent_test

ComplexTypes:
	componentType