mtpti5iD/redhat-docs_dataset huggingface dataset:
8.4. augeas 8.4.1. RHSA-2013:1537 - Low: augeas security, bug fix, and enhancement update Updated augeas packages that fix two security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, are available for each vulnerability from the CVE links associated with each description below. Augeas is a utility for editing configuration. Augeas parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native configuration files. Augeas also uses "lenses" as basic building blocks for establishing the mapping from files into the Augeas tree and back. Security Fix CVE-2012-0786 , CVE-2012-0787 Multiple flaws were found in the way Augeas handled configuration files when updating them. An application using Augeas to update configuration files in a directory that is writable to by a different user (for example, an application running as root that is updating files in a directory owned by a non-root service user) could have been tricked into overwriting arbitrary files or leaking information via a symbolic link or mount point attack. Note The augeas package has been upgraded to upstream version 1.0.0, which provides a number of bug fixes and enhancements over the version. (BZ# 817753 ) Bug Fixes BZ# 799885 Previously, when single quotes were used in an XML attribute, Augeas was unable to parse the file with the XML lens. An upstream patch has been provided ensuring that single quotes are handled as valid characters and parsing no longer fails. BZ# 855022 Prior to this update, Augeas was unable to set up the "require_ssl_reuse" option in the vsftpd.conf file. The updated patch fixes the vsftpd lens to properly recognize this option, thus fixing this bug. BZ# 799879 Previously, the XML lens did not support non-Unix line endings. Consequently, Augeas was unable to load any files containing such line endings. The XML lens has been fixed to handle files with CRLF line endings, thus fixing this bug. BZ# 826752 Previously, Augeas was unable to parse modprobe.conf files with spaces around "=" characters in option directives. The modprobe lens has been updated and parsing no longer fails. All Augeas users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements.

Commands:
Chapter 2. Scanning a software bill of materials file You can scan your custom software bill of materials (SBOM) manifest files for analysis by Red Hat. Important Red Hat does not retain a copy of your scanned SBOM files. Prerequisites A Red Hat user account to access the Red Hat Hybrid Cloud Console . An existing CycloneDX 1.3, 1.4, or 1.5 or Software Package Data Exchange (SPDX) 2.2, 2.3 manifest files. Procedure Open a web browser. Go to the Application and Data Services home page on the Hybrid Cloud Console. If prompted, log in to the Hybrid Cloud Console with your credentials. On the navigation menu, click Trusted Profile Analyzer . On the Trusted Profile Analyzer home page, click the Subscribe and launch button. A new web browser window opens to the Trusted Profile Analyzer console home page. Note By subscribing, your registered email address goes onto the product mailing list, so you can receive information about new product developments. Click Scan SBOM from the navigation menu. You can drag-and-drop an SBOM manifest file onto the page, or click Load an SBOM . After scanning the SBOM file, you get a summary of the analysis, and specific vulnerability information for the packages included in your SBOM file. Additional resources To learn how to create a software bill of materials file, see the Trusted Profile Analyzer Reference Guide for details.

Commands:
4.300. spice-client 4.300.1. RHBA-2012:0371 - spice-client bug fix update An updated spice-client package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The spice-client package provides the Simple Protocol for Independent Computing Environments (SPICE) client application. SPICE is a remote display protocol designed for virtual environments. SPICE users can access a virtualized desktop or server from the local system or any system with network access to the server. SPICE is used in Red Hat Enterprise Linux for viewing virtualized guests running on the KVM hypervisor or on Red Hat Enterprise Virtualization Hypervisors. Bug Fixes BZ# 771323 The SPICE client did not properly support the Xinerama extension in full screen mode on multi-screen setups. Therefore, if the user switched to full screen mode while using Xinerama, the SPICE client windows failed to cover all physical screens used by the guest. With this update, the underlying code has been modified to provide Xinerama support and the SPICE client now behaves correctly in full screen mode. BZ# 790892 Any attempt of sound recording in the guest failed if there was another application accessing the recording device on the SPICE client startup. This update ensures that the client uses the PulseAudio sound server, which now allows multiple applications to access the recording device at the same time. All users of spice-client are advised to upgrade to this updated package, which fixes these bugs.

Commands:
5.2. Top-level Files within the proc File System Below is a list of some of the more useful virtual files in the top-level of the /proc/ directory. Note In most cases, the content of the files listed in this section are not the same as those installed on your machine. This is because much of the information is specific to the hardware on which Red Hat Enterprise Linux is running for this documentation effort. 5.2.1. /proc/apm This file provides information about the state of the Advanced Power Management (APM) system and is used by the apm command. If a system with no battery is connected to an AC power source, this virtual file would look similar to the following: Running the apm -v command on such a system results in output similar to the following: For systems which do not use a battery as a power source, apm is able do little more than put the machine in standby mode. The apm command is much more useful on laptops. For example, the following output is from the command cat /proc/apm on a laptop while plugged into a power outlet: When the same laptop is unplugged from its power source for a few minutes, the content of the apm file changes to something like the following: The apm -v command now yields more useful data, such as the following:

Commands:
1.16 1.2 0x07 0x01 0xff 0x80 -1% -1 ?
APM BIOS 1.2 (kernel driver 1.16ac) AC on-line, no system battery
1.16 1.2 0x03 0x01 0x03 0x09 100% -1 ?
1.16 1.2 0x03 0x00 0x00 0x01 99% 1792 min
APM BIOS 1.2 (kernel driver 1.16) AC off-line, battery status high: 99% (1 day, 5:52)
Chapter 4. Publishing applications with .NET 6.0 .NET 6.0 applications can be published to use a shared system-wide version of .NET or to include .NET. The following methods exist for publishing .NET 6.0 applications: Single-file application - The application is self-contained and can be deployed as a single executable with all dependent files contained in a single binary. Note Single-file application deployment is not available on IBM Z and LinuxONE. Framework-dependent deployment (FDD) - The application uses a shared system-wide version of .NET. Note When publishing an application for RHEL, Red Hat recommends using FDD, because it ensures that the application is using an up-to-date version of .NET, built by Red Hat, that uses a set of native dependencies. Self-contained deployment (SCD) - The application includes .NET. This method uses a runtime built by Microsoft. Note SCD is not available on IBM Z and LinuxONE. Prerequisites Existing .NET application. For more information on how to create a .NET application, see Creating an application using .NET . 4.1. Publishing .NET applications The following procedure outlines how to publish a framework-dependent application. Procedure Publish the framework-dependent application: Replace my-app with the name of the application you want to publish. Optional: If the application is for RHEL only, trim out the dependencies needed for other platforms: Replace architecture based on the platform you are using: For Intel: x64 For IBM Z and LinuxONE: s390x For 64-bit Arm: arm64

Commands:
dotnet publish my-app -f net6.0 -c Release
dotnet publish my-app -f net6.0 -c Release -r rhel.9- architecture --self-contained false
Chapter 5. Managing DHCP using Capsule Satellite can integrate with a DHCP service using your Capsule. A Capsule has multiple DHCP providers that you can use to integrate Satellite with your existing DHCP infrastructure or deploy a new one. You can use the DHCP module of Capsule to query for available IP addresses, add new, and delete existing reservations. Note that your Capsule cannot manage subnet declarations. Available DHCP providers dhcp_infoblox - For more information, see Using Infoblox as DHCP and DNS Providers in Provisioning hosts . dhcp_isc - ISC DHCP server over OMAPI. For more information, see Configuring DNS, DHCP, and TFTP on Capsule Server in Installing Capsule Server . dhcp_remote_isc - ISC DHCP server over OMAPI with leases mounted through networking. For more information, see Configuring an External DHCP Server to Use with Capsule Server in Installing Capsule Server . 5.1. Securing the dhcpd API Capsule interacts with DHCP daemon using the dhcpd API to manage DHCP. By default, the dhcpd API listens to any host without access control. You can add an omapi_key to provide basic security. Procedure On your Capsule, install the required packages: Generate a key: Use satellite-installer to secure the dhcpd API:

Commands:
satellite-maintain packages install bind-utils
dnssec-keygen -r /dev/urandom -a HMAC-MD5 -b 512 -n HOST omapi_key cat Komapi_key.+*.private | grep ^Key|cut -d ' ' -f2-
satellite-installer --foreman-proxy-dhcp-key-name " My_Name " --foreman-proxy-dhcp-key-secret " My_Secret "
13.9.2. Useful Websites http://www.openldap.org/ - Home of the OpenLDAP Project. This website contains a wealth of information about configuring OpenLDAP as well as a future roadmap and version changes. http://www.redhat.com/mirrors/LDP/HOWTO/LDAP-HOWTO.html - A comprehensive, relevant, and updated LDAP HOWTO. http://www.padl.com/ - Developers of nss_ldap and pam_ldap , among other useful LDAP tools. http://www.kingsmountain.com/ldapRoadmap.shtml - Jeff Hodges' LDAP Road Map contains links to several useful FAQs and emerging news concerning the LDAP protocol. http://www.newarchitectmag.com/archives/2000/05/wilcox/ - A useful look at managing groups in LDAP. http://www.ldapman.org/articles/ - Articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.

Commands:
8.29. clustermon 8.29.1. RHBA-2014:1582 - clustermon bug fix update Updated clustermon packages that fix one bug are now available for Red Hat Enterprise Linux 6. The clustermon packages are used for remote cluster management. The modclusterd service provides an abstraction of cluster status used by the Conga architecture and by the Simple Network Management (SNMP) and Common Information Model (CIM) modules of clustermon. Bug Fix BZ# 1076716 Previously, the modcluster service mishandled requests with size in bytes divisible by 4096, which is the size of the read buffer in bytes. Consequently, modcluster incorrectly evaluated such requests as errors. This bug has been fixed, and modcluster now processes all requests as expected. Users of clustermon are advised to upgrade to these updated packages, which fix this bug.

Commands:
11.6. Do You Have Enough Disk Space? Nearly every modern-day operating system (OS) uses disk partitions , and Red Hat Enterprise Linux is no exception. When you install Red Hat Enterprise Linux, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to Appendix A, An Introduction to Disk Partitions before proceeding. The disk space used by Red Hat Enterprise Linux must be separate from the disk space used by other OSes you may have installed on your system. Before you start the installation process, you must have enough unpartitioned [6] disk space for the installation of Red Hat Enterprise Linux, or have one or more partitions that may be deleted, thereby freeing up enough disk space to install Red Hat Enterprise Linux. To gain a better sense of how much space you really need, refer to the recommended partitioning sizes discussed in Section 16.17.5, "Recommended Partitioning Scheme" . [6] Unpartitioned disk space means that available disk space on the hard drives you are installing to has not been divided into sections for data. When you partition a disk, each partition behaves like a separate disk drive.

Commands:
14.6. Viewing Security Domain Configuration A security domain is a registry of PKI services. PKI services, such as CAs, register information about themselves in these domains so users of PKI services can find other services by inspecting the registry. The security domain service in Certificate System manages both the registration of PKI services for Certificate System subsystems and a set of shared trust policies. The security domain manages the trust relationships between subsystems automatically, so if a TPS, TKS, and KRA are within the same security domain, they can communicate securely. Note The security domain is used during subsystem configuration. When a subsystem is being set up, it can check the security domain registry to see available instances. If it needs to create a trusted relationship with another instance - like a TPS which uses a TKS and KRA for its operations - then the security domain is used to create a TPS agent user on the selected TKS and KRA instances. The registry provides a complete view of all PKI services provided by the subsystems within that domain. Each Certificate System subsystem must be either a host or a member of a security domain. Only a CA can host and manage a security domain. Each CA has its own LDAP entry, and the security domain is an organizational group underneath that CA entry: Then there is a list of each subsystem type beneath the security domain organizational group, with a special object class ( pkiSecurityGroup ) to identify the group type: Each subsystem instance is then stored as a member of that group, with a special pkiSubsystem object class to identify the entry type:

Commands:
ou=Security Domain,dc=example,dc=com
cn=KRAList,ou=Security Domain,dc=example,dc=com objectClass: top objectClass: pkiSecurityGroup cn: KRAList
dn: cn=server.example.com:8443,cn=KRAList,ou=Security Domain,dc=example,dc=com objectClass: top objectClass: pkiSubsystem cn: kra.example.com:8443 host: server.example.com SecurePort: 8443 SecureAgentPort: 8443 SecureAdminPort: 8443 UnSecurePort: 8080 DomainManager: false Clone: false SubsystemName: KRA server.example.com 8443
Chapter 4. Networking and Services 4.1. Interfaces and Configuration NetworkManager Red Hat Enterprise Linux 6 uses NetworkManager by default when configuring network interfaces; however, the network configuration tools, system-config-network , system-config-network-tui and system-config-network-cmd are still included. Infiniband Infiniband support (specifically the openib start script and the openib.conf file) was provided by the openib package in Red Hat Enterprise Linux 5. The package name has changed in Red Hat Enterprise Linux 6 to reflect its functionality more accurately. The Infiniband functionality is now distributed in the rdma package. The service is now called rdma , and the configuration file is located at /etc/rdma/rdma.conf . biosdevname biosdevname accepts a kernel device name as an argument, and returns the BIOS-assigned name for that device. This is useful on systems where the BIOS name for a device does not directly or clearly map to the kernel name. The use of biosdevname is only recommended on systems and architectures that provide such information in their BIOS. Pass biosdevname=1 at installation time to activate biosdevname based naming.

Commands:
15.4. Setting up Active Directory for Synchronization Synchronizing user accounts alone is enabled within IdM, so all that is necessary is to set up a sync agreement ( Section 15.5.2, "Creating Synchronization Agreements" ). However, the Active Directory does need to be configured in a way that allows the Identity Management server to connect to it. 15.4.1. Creating an Active Directory User for Sync On the Windows server, it is necessary to create the user that the IdM server will use to connect to the Active Directory domain. The process for creating a user in Active Directory is covered in the Windows server documentation at http://technet.microsoft.com/en-us/library/cc732336.aspx . The new user account must have the proper permissions: Grant the sync user account Replicating directory changes rights to the synchronized Active Directory subtree. Replicator rights are required for the sync user to perform synchronization operations. Replicator rights are described in http://support.microsoft.com/kb/303972 . Add the sync user as a member of the Account Operator and Enterprise Read-Only Domain controller groups. It is not necessary for the user to belong to the full Domain Admin group. 15.4.2. Setting up an Active Directory Certificate Authority The Identity Management server connects to the Active Directory server using a secure connection. This requires that the Active Directory server have an available CA certificate or CA certificate chain available, which can be imported into the Identity Management security databases, so that the Windows server is a trusted peer. While this could technically be done with an external (to Active Directory) CA, most deployments should use the Certificate Services available with Active Directory. The procedure for setting up and configuring certificate services on Active Directory is covered in the Microsoft documentation at http://technet.microsoft.com/en-us/library/cc772393(v=WS.10).aspx .

Commands:
32.8.4. Running subscription-manager as a Post-Install Script The subscription-manager command-line script registers a system to a Red Hat Subscription Management server (Customer Portal Subscription Management, Subscription Asset Manager, or CloudForms System Engine). This script can also be used to assign or attach subscriptions automatically to the system that best-match that system. When registering to the Customer Portal, use the Red Hat network login credentials. When registering to Subscription Asset Manager or CloudForms System Engine, use whatever user account was created by the local administrator. Additional options can be used with the registration command to set a preferred service level for the system and to restrict updates and errata to a specific operating system version. For additional information about using subscription-manager , see the Knowledgebase article at https://access.redhat.com/solutions/748313 .

Commands:
%post --log=/root/ks-post.log /usr/sbin/subscription-manager register --username=admin@example.com --password=secret --serverurl=sam-server.example.com --org="Admin Group" --environment="Dev" --servicelevel=standard --release="6.6" %end
Chapter 3. Result Set Caching 3.1. User Query Cache User query result set caching will cache result sets based on an exact match of the incoming SQL string and PreparedStatement parameter values if present. Caching only applies to SELECT, set query, and stored procedure execution statements; it does not apply to SELECT INTO statements, or INSERT, UPDATE, or DELETE statements. End users or client applications explicitly state whether to use result set caching. Do this by setting the JDBC ResultSetCacheMode execution property to true (by default it is set to false). Alternatively, add a Cache Hint to the query. Note Note that if either of these mechanisms are used, DV must also have result set caching enabled (it is so by default). The most basic form of the cache hint, /*+ cache */, is sufficient to inform the engine that the results of the non-update command must be cached. The results will be cached with the default ttl and use the SQL string and the parameter value as part of the cache key. The pref_mem and ttl options of the cache hint may also be used for result set cache queries. If a cache hint is not specified, then the default time to live of the result set caching configuration will be used. Here is a more advanced example: In this example the memory preference has been enabled and the time to live is set to 60000 milliseconds (1 minute). The time-to-live for an entry is actually treated as its maximum age and the entry may be purged sooner if the maximum number of cache entries has been reached. Important Each query is re-checked for authorization using the current user's permissions, regardless of whether or not the results have been cached.

Commands:
Properties info = new Properties(); info.setProperty("ResultSetCacheMode", "true"); Connection conn = DriverManager.getConnection(url, info);
PreparedStatement ps = connection.prepareStatement("/*+ cache */ select col from t where col2 = ?"); ps.setInt(1, 5); ps.execute();
/*+ cache(pref_mem ttl:60000) */ select col from t