mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 20. Managing User Authentication When a user connects to the Red Hat Directory Server, first the user is authenticated. Then, the directory grants access rights and resource limits to the user depending upon the identity established during authentication. This chapter describes tasks for managing users, including configuring the password and account lockout policy for the directory, denying groups of users access to the directory, and limiting system resources available to users depending upon their bind DNs. 20.1. Setting User Passwords You can use an entry to bind to the directory only if it has a userPassword attribute and if it has not been inactivated. Because user passwords are stored in the directory, the user passwords can be set or reset with any LDAP operation, such as using the ldapmodify utility. When an administrator changes the password of a user, Directory Server sets the pwdReset operational attribute in the user's entry to true . Applications can use this attribute to identify if a password of a user has been reset by an administrator. For information on creating and modifying directory entries, see Chapter 3, Managing Directory Entries . For information on inactivating user accounts, see Section 20.16, "Manually Inactivating Users and Roles" . Only password administrators, described in Section 20.2, "Setting Password Administrators" , and the root DN can add pre-hashed passwords. These users can also violate password policies. Warning When using a password administrator account or the Directory Manager (root DN) to set a password, password policies are bypassed and not verified. Do not use these accounts for regular user password management. Use them only to perform password administration tasks that require bypassing the password policies.

Commands:
Appendix A. Updating the Local Repository for an Offline Red Hat Virtualization Manager Installation If your Red Hat Virtualization Manager is hosted on a machine that receives packages via FTP from a local repository, you must regularly synchronize the repository to download package updates from the Content Delivery Network, then update or upgrade that machine. Updated packages address security issues, fix bugs, and add enhancements. On the system hosting the repository, synchronize the repository to download the most recent version of each available package: # reposync --newest-only -p /var/ftp/pub/rhevrepo This command might download a large number of packages, and take a long time to complete. Ensure that the repository is available on the Manager machine, and then update or upgrade the machine.

Commands:
reposync --newest-only -p /var/ftp/pub/rhevrepo
5.259. python-paste-script 5.259.1. RHSA-2012:1206 - Moderate: python-paste-script security update An updated python-paste-script package that fixes one security issue is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Python Paste provides middleware for building and running Python web applications. The python-paste-script package includes paster, a tool for working with and running Python Paste applications. Security Fix CVE-2012-0878 It was discovered that paster did not drop supplementary group privileges when started by the root user. Running "paster serve" as root to start a Python web application that will run as a non-root user and group resulted in that application running with root group privileges. This could possibly allow a remote attacker to gain access to files that should not be accessible to the application. All paster users should upgrade to this updated package, which contains a backported patch to resolve this issue. All running paster instances configured to drop privileges must be restarted for this update to take effect.

Commands:
2.45. RHEA-2011:0727 - new package: system-switch-java A new system-switch-java package is now available for Red Hat Enterprise Linux 6. The system-switch-java package provides a tool that allows you to select the Java environment you want to use from the list of the installed Java alternatives. The tool supports a graphical user interface (GUI) and text user interface (TUI) mode. This enhancement update adds the system-switch-java package to Red Hat Enterprise Linux 6. (BZ# 663322 ) All users who require system-switch-java should install this new package.

Commands:
Chapter 2. Before Configuring a Red Hat Cluster This chapter describes tasks to perform and considerations to make before installing and configuring a Red Hat Cluster, and consists of the following sections: Section 2.1, "Compatible Hardware" Section 2.2, "Enabling IP Ports" Section 2.3, "Configuring ACPI For Use with Integrated Fence Devices" Section 2.4, "Configuring max_luns" Section 2.5, "Considerations for Using Quorum Disk" Section 2.7, "Considerations for Using Conga " Section 2.8, "General Configuration Considerations" 2.1. Compatible Hardware Before configuring Red Hat Cluster software, make sure that your cluster uses appropriate hardware (for example, supported fence devices, storage devices, and Fibre Channel switches). Refer to the hardware configuration guidelines at http://www.redhat.com/cluster_suite/hardware/ for the most current hardware compatibility information.

Commands:
Chapter 25. OpenShift by Red Hat OpenShift by Red Hat is a Platform as a Service (PaaS) that enables developers to build and deploy web applications. OpenShift provides a wide selection of programming languages and frameworks including Java, Ruby, and PHP. It also provides integrated developer tools to support the application life cycle, including Eclipse integration, JBoss Developer Studio, and Jenkins. OpenShift uses an open source ecosystem to provide a platform for mobile applications, database services, and more. [24] In Red Hat Enterprise Linux, the openshift-clients package provides the OpenShift client tools. Enter the following command to see if it is installed: If the openshift-clients package is not installed, see the OpenShift Enterprise Client Tools Installation Guide and OpenShift Online Client Tools Installation Guide for detailed information on the OpenShift client tools installation process. Important Previously, the rhc package provided the OpenShift client tools. With the latest OpenShift versions, this package has been deprecated and is no longer supported by Red Hat. Hence, after OpenShift version 2, the rhc package is replaced with the openshift-clients package that provides the OpenShift client tools used for supported OpenShift versions. 25.1. OpenShift and SELinux SELinux provides better security control over applications that use OpenShift because all processes are labeled according to the SELinux policy. Therefore, SELinux protects OpenShift from possible malicious attacks within different gears running on the same node. See the Dan Walsh's presentation for more information about SELinux and OpenShift. [24] To learn more about OpenShift, see Product Documentation for OpenShift Container Platform and Product Documentation for OpenShift Online .

Commands:
~]USD rpm -q openshift-clients package openshift-clients is not installed
D.12. Context Menu Additional actions are available by selecting a problem and right-click to open a context menu. Figure D.22. Problems View Context Menu Go To - will open the appropriate editor and select the affected/referenced object. Show In Navigator - Opens the Basic > Navigator view (if not open) and expands file system tree and reveals applicable resource. Copy - Copies the problem information to the system clipboard. Delete - Deletes the selected problem rows ( if applicable ). Select All - selects all problems in the table. Quick Fix - (Not yet implemented in Teiid Designer). Properties - displays a dialog containing additional information.

Commands:
Chapter 58. Networking Verification of signatures using the MD5 hash algorithm is disabled in Red Hat Enterprise Linux 7 It is impossible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5 signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Then run the systemctl daemon-reload command as root to reload the service file. Important: Note that MD5 certificates are highly insecure and Red Hat does not recommend using them. (BZ#1062656)

Commands:
Environment=OPENSSL_ENABLE_MD5_VERIFY=1
21.4. Parameters for Kickstart Installations The following parameters can be defined in a parameter file but do not work in a CMS configuration file. inst.ks= URL References a Kickstart file, which usually resides on the network for Linux installations on IBM Z. Replace URL with the full path including the file name of the Kickstart file. This parameter activates automatic installation with Kickstart. See Kickstart Boot Options and Section 27.2.5, "Starting the Kickstart Installation" for more details. RUNKS= value Important This parameter is deprecated. If you use it in a Kickstart file, it will be ignored. Only the inst.ks= parameter is necessary to start a Kickstart installation on IBM Z. Where value is defined as 1 if you want to run the loader automatically on the Linux console without having to log in over the network with SSH. To use RUNKS=1 , the console must either support full-screen or the inst.cmdline option (below) should be used. The latter applies for the 3270 terminal under z/VM or the operating system messages console for LPAR. We recommend RUNKS=1 for fully automatic installations with Kickstart. When RUNKS=1 is set, the installation program automatically continues in case of parameter errors and does not interrupt unattended installations by prompting for user interaction. Leave out the parameter or specify RUNKS=0 otherwise. inst.cmdline When this option is specified, output on line-mode terminals (such as 3270 under z/VM or operating system messages for LPAR) becomes readable, as the installation program disables escape terminal sequences that are only applicable to UNIX-like consoles. This requires installation with a Kickstart file that answers all questions, because the installation program does not support interactive user input in cmdline mode. Ensure that your Kickstart file contains all required parameters before you use the inst.cmdline option. If a required command is missing, the installation will fail. See Chapter 27, Kickstart Installations for details.

Commands:
function::user_ulong Name function::user_ulong - Retrieves an unsigned long value stored in user space Synopsis Arguments addr the user space address to retrieve the unsigned long from Description Returns the unsigned long value from a given user space address. Returns zero when user space data is not accessible. Note that the size of the unsigned long depends on the architecture of the current user space task (for those architectures that support both 64/32 bit compat tasks).

Commands:
user_ulong:long(addr:long)
7.99. kdebase-workspace 7.99.1. RHBA-2012:1286 - kdebase-workspace bug fix update Updated kdebase-workspace packages that fix one bug are now available for Red Hat Enterprise Linux 6. The kdebase-workspace packages contain utilities for basic operations with the desktop environment. The utilities allow users for example, to change system settings, resize and rotate X screens or set panels and widgets on the workspace. Bug Fix BZ#749460 Prior to this update, the task manager did not honor the order of manually arranged items. As a consequence, manually arranged taskbar entries were randomly rearranged when the user switched desktops. This update modifies the underlying code to make manually arranged items more persistent. All users of kdebase-workspace are advised to upgrade to these updated packages, which fix this bug.

Commands:
3.7. Configuring IP Networking from the Kernel Command line When connecting to the root file system on an iSCSI target from an interface, the network settings are not configured on the installed system. For solution of this problem: Install the dracut utility. For information on using dracut , see Red Hat Enterprise Linux System Administrator's Guide Set the configuration using the ip option on the kernel command line: dhcp - DHCP configuration dhpc6 - DHCP IPv6 configuration auto6 - automatic IPv6 configuration on , any - any protocol available in the kernel (default) none , off - no autoconfiguration, static network configuration For example: Set the name server configuration: The dracut utility sets up a network connection and generates new ifcfg files that can be copied to the /etc/sysconfig/network-scripts/ file.

Commands:
ip<client-IP-number>:[<server-id>]:<gateway-IP-number>:<netmask>:<client-hostname>:<interface>:{dhcp|dhcp6|auto6|on|any|none|off}
ip=192.168.180.120:192.168.180.100:192.168.180.1:255.255.255.0::enp1s0:off
nameserver=srv1 [nameserver=srv2 [nameserver=srv3 [...]]]
Chapter 3. Enabling plugins added in the RHDH container image In the RHDH container image, a set of dynamic plugins is preloaded to enhance functionality. However, due to mandatory configuration requirements, most of the plugins are disabled. You can enable and configure the plugins in the RHDH container image, including how to manage the default configuration, set necessary environment variables, and ensure the proper functionality of the plugins within your application. Prerequisites You have access to the dynamic-plugins.default.yaml file, which lists all preloaded plugins and their default configuration. You have deployed the RHDH application, and have access to the logs of the install-dynamic-plugins init container. You have the necessary permissions to modify plugin configurations and access the application environment. You have identified and set the required environment variables referenced by the plugin's default configuration. These environment variables must be defined in the Helm Chart or Operator configuration. Procedure Start your RHDH application and access the logs of the install-dynamic-plugins init container within the RHDH pod. Identify the Red Hat supported plugins that are disabled by default. Copy the package configuration from the dynamic-plugins.default.yaml file. Open the plugin configuration file and locate the plugin entry you want to enable. The location of the plugin configuration file varies based on the deployment method. For more details, see Installing dynamic plugins with the Red Hat Developer Hub Operator and Installing dynamic plugins using the Helm chart . Modify the disabled field to false and add the package name as follows: Example plugin configuration plugins: - disabled: false package: ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic For more information about how to configure dynamic plugins in Developer Hub, see Installing dynamic plugins in Red Hat Developer Hub . Verification Restart the RHDH application and verify that the plugin is successfully activated and configured. Verify the application logs for confirmation and ensure the plugin is functioning as expected.

Commands:
plugins: - disabled: false package: ./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-github-dynamic
Chapter 1. Policy APIs 1.1. Eviction [policy/v1] Description Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to ... /pods/<pod name>/evictions. Type object 1.2. PodDisruptionBudget [policy/v1] Description PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods Type object

Commands:
6.3. Setting up Browsers to Support SSL for Tokens In Mozilla Firefox, open the Edit menu, choose Preferences , and then click Advanced . Open the Encryption tab. Add a PKCS #11 driver. Click Security Devices to open the Device Manager window, and then click the Load button. Enter a module name, such as token key pk11 driver . Click Browse , find the Enterprise Security Client PKCS #11 driver, and click OK . The PKCS #11 module used by these applications, by default, is located in /usr/lib/libcoolkeypk11.so . If the CA is not yet trusted, download and import the CA certificate. Open the SSL End Entity page on the CA. For example: Click the Retrieval tab, and then click Import CA Certificate Chain . Click Download the CA certificate chain in binary form and then click Submit . Choose a suitable directory to save the certificate chain, and then click OK . Click Edit > Preferences , and select the Advanced tab. Click the View Certificates button. Click Authorities , and import the CA certificate. Set the certificate trust relationships. Click Edit > Preferences , and select the Advanced tab. Click the View Certificates button. Click Edit , and set the trust for websites. The certificates can be used for SSL.

Commands:
http s ://server.example.com: 9444/ca/ee/ca/
A. Revision History Revision History Revision 2-11 Mon Aug 19 2019 Jaromir Hradilek Preparing document for 7.7 GA publication Revision 2-10 Wed May 29 2019 Sharon Moroney Preparing document for 7.7 Beta publication Revision 2-9 Tue Oct 30 2018 Vladimir Slavik Preparing document for 7.6 GA publication Revision 2-8 Tue Aug 21 2018 Vladimir Slavik Preparing document for 7.6 Beta publication Revision 2-7 Fri Apr 6 2018 Petr Bokoc Preparing document for 7.5 GA publication Revision 2-6 Fri Dec 15 2017 Petr Bokoc Preparing document for 7.5 Beta publication Revision 2-5 Tue Aug 1 2017 Petr Bokoc Preparing document for 7.4 GA publication Revision 2-4 Tue May 16 2017 Petr Bokoc Preparing document for 7.4 Beta publication Revision 2-3 Mon May 15 2017 Petr Bokoc Asynchronous update Revision 2-2 Mon Nov 16 2015 Petr Bokoc Version for Red Hat Enterprise Linux 7.2 GA release Revision 2-1 Mon Jun 22 2015 Petr Bokoc Finished editing the Anaconda Add-on Development section Added a section on customizing Anaconda visuals Revision 2-0 Fri Jun 19 2015 Petr Bokoc Changed book title to Anaconda Customization Guide Added section about unpacking and repacking ISO images Added section about customizing boot menu Edited most of the Anaconda Add-on Development section for better readability Revision 1-0 Wed Jan 15 2014 Vratislav Podzimek First version to be a part of the official documentation Revision 0-0 Fri Dec 28 2012 Vratislav Podzimek Initial creation of book by publican

Commands:
6.2. Preparing for a Driver Update During Installation If a driver update is necessary and available for your hardware, Red Hat or a trusted third party such as the hardware vendor will typically provide it in the form of an image file in ISO format. Some methods of performing a driver update require you to make the image file available to the installation program, while others require you to use the image file to make a driver update disk: Methods that use the image file itself local hard drive USB flash drive Methods that use a driver update disk produced from an image file CD DVD Choose a method to provide the driver update, and refer to Section 6.2.1, "Preparing to Use a Driver Update Image File" , Section 6.2.2, "Preparing a Driver Disc" or Section 6.2.3, "Preparing an Initial RAM Disk Update" . Note that you can use a USB storage device either to provide an image file, or as a driver update disk. 6.2.1. Preparing to Use a Driver Update Image File 6.2.1.1. Preparing to use an image file on local storage To make the ISO image file available on local storage, such as a hard drive or USB flash drive, you must first determine whether you want to install the updates automatically or select them manually. For manual installations, copy the file onto the storage device. You can rename the file if you find it helpful to do so, but you must not change the filename extension, which must remain .iso . In the following example, the file is named dd.iso : Figure 6.1. Content of a USB flash drive holding a driver update image file Note that if you use this method, the storage device will contain only a single file. This differs from driver discs on formats such as CD and DVD, which contain many files. The ISO image file contains all of the files that would normally be on a driver disc. Refer to Section 6.3.2, "Let the Installer Prompt You for a Driver Update" and Section 6.3.3, "Use a Boot Option to Specify a Driver Update Disk" to learn how to select the driver update manually during installation. For automatic installations, you will need to extract the ISO to the root directory of the storage device rather than copy it. Copying the ISO is only effective for manual installations. You must also change the file system label of the device to OEMDRV . The installation program will then automatically examine the extracted ISO for driver updates and load any that it detects. This behavior is controlled by the dlabel=on boot option, which is enabled by default. Refer to Section 6.3.1, "Let the Installer Find a Driver Update Disk Automatically" .

Commands:
23.3. SMBIOS System Information Some hypervisors allow control over what system information is presented to the guest virtual machine (for example, SMBIOS fields can be populated by a hypervisor and inspected using the dmidecode command in the guest virtual machine). The optional sysinfo element covers all such categories of information. ... <os> <smbios mode='sysinfo'/> ... </os> <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> </bios> <system> <entry name='manufacturer'>Fedora</entry> <entry name='vendor'>Virt-Manager</entry> </system> </sysinfo> ... Figure 23.5. SMBIOS system information The <sysinfo> element has a mandatory attribute type that determines the layout of sub-elements, and may be defined as follows: <smbios> - Sub-elements call out specific SMBIOS values, which will affect the guest virtual machine if used in conjunction with the smbios sub-element of the <os> element. Each sub-element of <sysinfo> names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized: <bios> - This is block 0 of SMBIOS, with entry names drawn from vendor , version , date , and release . <system> - This is block 1 of SMBIOS, with entry names drawn from manufacturer , product , version , serial , uuid , sku , and family . If a uuid entry is provided alongside a top-level uuid element, the two values must match.

Commands:
<os> <smbios mode='sysinfo'/> </os> <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> </bios> <system> <entry name='manufacturer'>Fedora</entry> <entry name='vendor'>Virt-Manager</entry> </system> </sysinfo>
3.7. Clustering corosync component, BZ# 722469 A double ring failure results in the spinning of the corosync process. Also, because DLM relies on SCTP, which is non-functional, many features of the cluster software that rely on DLM do not work properly. luci component, BZ# 615898 luci will not function with Red Hat Enterprise Linux 5 clusters unless each cluster node has ricci version 0.12.2-14.

Commands: