mtpti5iD/redhat-docs_dataset huggingface dataset:
4.185. mysql 4.185.1. RHSA-2012:0105 - Important: mysql security update Updated mysql packages that fix several security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. 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. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. Bug Fixes CVE-2011-2262 , CVE-2012-0075 , CVE-2012-0087 , CVE-2012-0101 , CVE-2012-0102 , CVE-2012-0112 , CVE-2012-0113 , CVE-2012-0114 , CVE-2012-0115 , CVE-2012-0116 , CVE-2012-0118 , CVE-2012-0119 , CVE-2012-0120 , CVE-2012-0484 , CVE-2012-0485 , CVE-2012-0490 , CVE-2012-0492 This update fixes several vulnerabilities in the MySQL database server. Information about these flaws can be found on the Oracle Critical Patch Update Advisory page. These updated packages upgrade MySQL to version 5.1.61. Refer to the MySQL release notes for a full list of changes: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html All MySQL users should upgrade to these updated packages, which correct these issues. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.

Commands:
Chapter 3. Launching a JBoss EAP instance The following procedures show launching a public JBoss EAP instance from the Amazon Web Services (AWS) marketplace and launching a JBoss EAP instance on Amazon EC2 Console. 3.1. Launching a JBoss EAP instance from the AWS marketplace The public JBoss EAP Amazon Machine Image (AMI), offered with the pay-as-you-go (PAYG) model, is available at the Amazon Web Services (AWS) marketplace. Prerequisite You have an AWS account. The Amazon Web Services CLI is installed and configured with your account credentials. Procedure Go to AWS marketplace at the URL: https://aws.amazon.com/marketplace . Search for "JBoss EAP" in the search bar. Filter the results by Publisher , selecting Red Hat Limited and Red Hat . Click the image you want to launch. Note If you are based in Europe, the Middle East, or Africa, select the image from the publisher "Red Hat Limited" , otherwise select the image from the publisher "Red Hat" . You are redirected to the software subscription page. Select the subscription settings and click Continue to Subscribe . Accept the terms by clicking Accept Terms , click Continue to Configuration . You are redirected to the configuration page. Select the configuration options and click Continue to Launch . You are directed to launch the software page. Review the launch configuration details and launch the instance by clicking Launch . 3.2. Launching JBoss EAP instance from private AMI using AWS EC2 Console You can launch a JBoss EAP instance on Amazon EC2 using the EC2 console. You can also launch an instance using the AWS Command Line Interface. See AWS CLI for more information. Prerequisites You have a Red Hat subscription. You have an AWS account. The Amazon Web Services CLI is installed and configured with your account credentials. Procedure Open the Amazon EC2 console . From the Amazon EC2 console, click AMIs . Search for jbeap AMI in Private images ,located in the Amazon Machine Images (AMIs) panel, and select the AMI. For example, RHEL-9-JBEAP-8.0.0_HVM_GA-20240909-x86_64-0-Access2-GP2 . Choose an instance type. See Supported Amazon EC2 Instance Types for more information on supported Amazon EC2 instance types. In the Configure Instance Details section, configure the instance settings. In the Advanced Details section, User data box, you can paste the sample script to run JBoss EAP when the instance is launched. Note If required, you can specify the storage, tag the instance, and configure the security group details. Click Review and Launch . This takes you directly to the Review Instance Launch page. Click Launch to choose a key pair and launch the instance. Note If you have not selected a key pair, you need to specify a key pair before you launch an instance.

Commands:
Chapter 2. Installing Prerequisite Components 2.1. Install Open JDK on Red Hat Enterprise Linux Install the OpenJDK package: To install it to alternatives, run these commands: As root, run the alternatives command for java : Select /usr/lib/jvm/jre-[VERSION]-openjdk/bin/java . Then do the same for javac : Select /usr/lib/jvm/java-[VERSION]-openjdk/bin/javac .

Commands:
install java-[VERSION]-openjdk-devel
sudo alternatives --install /usr/bin/java java usr/lib/jvm/java-[VERSION]-openjdk/bin/java 1000
sudo alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-[VERSION]-openjdk/bin/javac 1000
/usr/sbin/alternatives --config java
/usr/sbin/alternatives --config javac
Chapter 6. Desktop LibreOffice rebased to version 4.3.7.2 The libreoffice packages have been upgraded to upstream version 4.3.7.2, which provides a number of bug fixes and enhancements over the version, including: The possibility to print comments in page margin has been added. Support for nested comments has been added. OpenXML interoperability has been improved. Accessibility support has been enhanced. The color picker has been improved. The start center has been improved. Initial HiDPI support has been added. The limitation on number of characters in a paragraph has been raised considerably. For a complete list of bug fixes and enhancements provided by this upgrade, refer to https://wiki.documentfoundation.org/ReleaseNotes/4.3. (BZ# 1258467 ) mesa now supports additional Intel 3D graphics The mesa package now supports integrated 3D graphics on 6th generation Intel Core processors, Intel Xeon processor E3 v5, and current Intel Pentium and Intel Celeron-branded processors. (BZ#1135362) New Vinagre features This update provides a number of features to Vinagre. Namely: The ability to connect through RDP protocol to remote Windows machines has been added. If requested, credentials can be stored in a keyring for RDP connections. Minimize button has been added to the fullscreen toolbar so that users do not need to leave fullscreen mode to minimize the whole window. In addition, the /apps/vinagre/plugins/active-plugins GConf key is now ignored as it could cause RDP not to be loaded. (BZ#1215093) vmwgfx now supports 3D operations under VMware Workstation 10 The vmwgfx driver has been updated to version 4.4, which enables vmwgfx support for 3D operations under VMware Workstation 10. With this upgrade, the vmwgfx driver now allows virtualized Red Hat Enterprise Linux 6 system to work as intended on Windows workstations. (BZ#1164447) x3270 rebased to version 3.3.15 The latest update of x3270 in Red Hat Enterprise Linux 6.8 adds support for oversize, dynamic screen resolutions, that is screen adjustment on window resizing, to the IBM 3270 terminal emulator for the X Window System. Viewing larger screen sizes thus works properly and larger files or outputs on the mainframe appear as expected. (BZ#1171849) icedtea-web rebased to version 1.6.2 The icedtea-web packages have been upgraded to upstream version 1.6.2, which provides a number of bug fixes and enhancements over the version. Notable changes include the following: The IcedTea-Web documentation and man pages have been significantly expanded. IcedTea-Web now supports bash completion. The Custom Policies and Run in Sandbox features have been enhanced. An -html switch has been implemented for the Java Web Start (JavaWS) framework, which can serve as a replacement of the AppletViewer program. It is now possible to use IcedTea-Web to create desktop and menu launchers for applets and JavaWS applications. (BZ#1275523)

Commands:
Part I. Getting started with Red Hat build of Kogito microservices As a developer of business decisions, you can use Red Hat build of Kogito business automation to develop decision services using Decision Model and Notation (DMN) models, Drools Rule Language (DRL) rules, Predictive Model Markup Language (PMML) or a combination of all three methods. Prerequisites JDK 11 or later is installed. Apache Maven 3.6.2 or later is installed.

Commands:
Chapter 18. Using NetworkManager to disable IPv6 for a specific connection On a system that uses NetworkManager to manage network interfaces, you can disable the IPv6 protocol if the network only uses IPv4. If you disable IPv6 , NetworkManager automatically sets the corresponding sysctl values in the Kernel. Note If disabling IPv6 using kernel tunables or kernel boot parameters, additional consideration must be given to system configuration. For more information, see the Red Hat Knowledgebase solution How do I disable or enable the IPv6 protocol in RHEL . 18.1. Disabling IPv6 on a connection using nmcli You can use the nmcli utility to disable the IPv6 protocol on the command line. Prerequisites The system uses NetworkManager to manage network interfaces. Procedure Optional: Display the list of network connections: Set the ipv6.method parameter of the connection to disabled : Restart the network connection: Verification Display the IP settings of the device: If no inet6 entry is displayed, IPv6 is disabled on the device. Verify that the /proc/sys/net/ipv6/conf/ enp1s0 /disable_ipv6 file now contains the value 1 : The value 1 means that IPv6 is disabled for the device.

Commands:
nmcli connection show NAME UUID TYPE DEVICE Example 7a7e0151-9c18-4e6f-89ee-65bb2d64d365 ethernet enp1s0
nmcli connection modify Example ipv6.method "disabled"
nmcli connection up Example
ip address show enp1s0 2: enp1s0 : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6b:74:be brd ff:ff:ff:ff:ff:ff inet 192.0.2.1/24 brd 192.10.2.255 scope global noprefixroute enp1s0 valid_lft forever preferred_lft forever
cat /proc/sys/net/ipv6/conf/ enp1s0 /disable_ipv6 1
Chapter 11. jndi 11.1. jndi:alias 11.1.1. Description Create a JNDI alias on a given name. 11.1.2. Syntax jndi:alias [options] name alias 11.1.3. Arguments Name Description name The JNDI name alias The JNDI alias 11.1.4. Options Name Description --help Display this help message 11.2. jndi:bind 11.2.1. Description Bind an OSGi service in the JNDI context 11.2.2. Syntax jndi:bind [options] service name 11.2.3. Arguments Name Description service The ID of the OSGi service to bind name The JNDI name to bind the OSGi service 11.2.4. Options Name Description --help Display this help message 11.3. jndi:contexts 11.3.1. Description List the JNDI sub-contexts. 11.3.2. Syntax jndi:contexts [options] [context] 11.3.3. Arguments Name Description context The base JNDI context 11.3.4. Options Name Description --help Display this help message 11.4. jndi:create 11.4.1. Description Create a new JNDI sub-context. 11.4.2. Syntax jndi:create [options] context 11.4.3. Arguments Name Description context The JNDI sub-context name 11.4.4. Options Name Description --help Display this help message 11.5. jndi:delete 11.5.1. Description Delete a JNDI sub-context. 11.5.2. Syntax jndi:delete [options] context 11.5.3. Arguments Name Description context The JNDI sub-context name 11.5.4. Options Name Description --help Display this help message 11.6. jndi:names 11.6.1. Description List the JNDI names. 11.6.2. Syntax jndi:names [options] [context] 11.6.3. Arguments Name Description context The JNDI context to display the names 11.6.4. Options Name Description --help Display this help message 11.7. jndi:unbind 11.7.1. Description Unbind a JNDI name. 11.7.2. Syntax jndi:unbind [options] name 11.7.3. Arguments Name Description name The JNDI name to unbind 11.7.4. Options Name Description --help Display this help message

Commands:
Appendix A. Component Versions This appendix is a list of components and their versions in the Red Hat Enterprise Linux 6.4 release. Table A.1. Component Versions Component Version Kernel 2.6.32-358 QLogic qla2xxx driver 8.04.00.08.06.4-k QLogic ql2xxx firmware ql23xx-firmware-3.03.27-3.1 ql2100-firmware-1.19.38-3.1 ql2200-firmware-2.02.08-3.1 ql2400-firmware-5.08.00-1 ql2500-firmware-5.08.00-1 Emulex lpfc driver 8.3.5.86.1p iSCSI initiator utils iscsi-initiator-utils-6.2.0.873-2 DM-Multipath device-mapper-multipath-0.4.9-64 LVM lvm2-2.02.98-9

Commands:
Appendix A. Revision History Revision History Revision 10.0-4 Fri Jul 14 2017 Steven Levine Update to version for 6.9 GA publication. Revision 10.0-2 Wed Mar 8 2017 Steven Levine Version for 6.9 GA publication. Revision 10.0-1 Fri Dec 16 2016 Steven Levine Version for 6.9 Beta publication. Revision 9.0-13 Tue Nov 8 2016 Steven Levine Small update for 6.8. Revision 9.0-12 Wed Apr 27 2016 Steven Levine Preparing document for 6.8 GA publication. Revision 9.0-10 Wed Mar 9 2016 Steven Levine Initial revision for Red Hat Enterprise Linux 6.8 Beta release Revision 8.0-5 Wed Jul 22 2015 Steven Levine Republish for Red Hat Enterprise Linux 6.7 Revision 8.0-4 Wed Jul 8 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Revision 8.0-3 Thu Apr 23 2015 Steven Levine Republish for Red Hat Enterprise Linux 6.7 Beta release Revision 7.0-4 Thu Aug 7 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Revision 7.0-3 Thu Aug 7 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Beta release Revision 6.0-6 Wed Nov 13 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Revision 6.0-5 Fri Sep 27 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Beta release Revision 5.0-9 Mon Feb 18 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.4 Revision 5.0-7 Mon Nov 26 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.4 Beta release Revision 4.0-3 Fri Jun 15 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.3 Revision 3.0-3 Thu Dec 1 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.2 Revision 3.0-1 Mon Sep 19 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.2 Beta release Revision 2.0-1 Thu May 19 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.1 Revision 1.0-1 Wed Nov 10 2010 Steven Levine Initial revision for the Red Hat Enterprise Linux 6 release

Commands:
Chapter 11. Enabling encryption on a vSphere cluster You can encrypt your virtual machines after installing OpenShift Container Platform 4.15 on vSphere by draining and shutting down your nodes one at a time. While each virtual machine is shutdown, you can enable encryption in the vCenter web interface. 11.1. Encrypting virtual machines You can encrypt your virtual machines with the following process. You can drain your virtual machines, power them down and encrypt them using the vCenter interface. Finally, you can create a storage class to use the encrypted storage. Prerequisites You have configured a Standard key provider in vSphere. For more information, see Adding a KMS to vCenter Server . Important The Native key provider in vCenter is not supported. For more information, see vSphere Native Key Provider Overview . You have enabled host encryption mode on all of the ESXi hosts that are hosting the cluster. For more information, see Enabling host encryption mode . You have a vSphere account which has all cryptographic privileges enabled. For more information, see Cryptographic Operations Privileges . Procedure Drain and cordon one of your nodes. For detailed instructions on node management, see "Working with Nodes". Shutdown the virtual machine associated with that node in the vCenter interface. Right-click on the virtual machine in the vCenter interface and select VM Policies Edit VM Storage Policies . Select an encrypted storage policy and select OK . Start the encrypted virtual machine in the vCenter interface. Repeat steps 1-5 for all nodes that you want to encrypt. Configure a storage class that uses the encrypted storage policy. For more information about configuring an encrypted storage class, see "VMware vSphere CSI Driver Operator". 11.2. Additional resources Working with nodes vSphere encryption Requirements for encrypting virtual machines

Commands:
5.9.5. Mounting File Systems Automatically with /etc/fstab When a Red Hat Enterprise Linux system is newly-installed, all the disk partitions defined and/or created during the installation are configured to be automatically mounted whenever the system boots. However, what happens when additional disk drives are added to a system after the installation is done? The answer is "nothing" because the system was not configured to mount them automatically. However, this is easily changed. The answer lies in the /etc/fstab file. This file is used to control what file systems are mounted when the system boots, as well as to supply default values for other file systems that may be mounted manually from time to time. Here is a sample /etc/fstab file: Each line represents one file system and contains the following fields: File system specifier -- For disk-based file systems, either a device file name ( /dev/sda1 ), a file system label specification ( LABEL=/ ), or a devlabel -managed symbolic link ( /dev/homedisk ) Mount point -- Except for swap partitions, this field specifies the mount point to be used when the file system is mounted ( /boot ) File system type -- The type of file system present on the specified device (note that auto may be specified to select automatic detection of the file system to be mounted, which is handy for removable media units such as diskette drives) Mount options -- A comma-separated list of options that can be used to control mount 's behavior ( noauto,owner,kudzu ) Dump frequency -- If the dump backup utility is used, the number in this field controls dump 's handling of the specified file system File system check order -- Controls the order in which the file system checker fsck checks the integrity of the file systems

Commands:
LABEL=/ / ext3 defaults 1 1 /dev/sda1 /boot ext3 defaults 1 2 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0 /dev/homedisk /home ext3 defaults 1 2 /dev/sda2 swap swap defaults 0 0
5.4.3.4. Changing Mirrored Volume Configuration You can increase or decrease the number of mirrors that a logical volume contains by using the lvconvert command. This allows you to convert a logical volume from a mirrored volume to a linear volume or from a linear volume to a mirrored volume. You can also use this command to reconfigure other mirror parameters of an existing logical volume, such as corelog . When you convert a linear volume to a mirrored volume, you are creating mirror legs for an existing volume. This means that your volume group must contain the devices and space for the mirror legs and for the mirror log. If you lose a leg of a mirror, LVM converts the volume to a linear volume so that you still have access to the volume, without the mirror redundancy. After you replace the leg, you can use the lvconvert command to restore the mirror. This procedure is provided in Section 7.3, "Recovering from LVM Mirror Failure" . The following command converts the linear logical volume vg00/lvol1 to a mirrored logical volume. The following command converts the mirrored logical volume vg00/lvol1 to a linear logical volume, removing the mirror leg. The following example adds an additional mirror leg to the existing logical volume vg00/lvol1 . This example shows the configuration of the volume before and after the lvconvert command changed the volume to a volume with two mirror legs.

Commands:
lvconvert -m1 vg00/lvol1
lvconvert -m0 vg00/lvol1
lvs -a -o name,copy_percent,devices vg00 LV Copy% Devices lvol1 100.00 lvol1_mimage_0(0),lvol1_mimage_1(0) [lvol1_mimage_0] /dev/sda1(0) [lvol1_mimage_1] /dev/sdb1(0) [lvol1_mlog] /dev/sdd1(0) lvconvert -m 2 vg00/lvol1 vg00/lvol1: Converted: 13.0% vg00/lvol1: Converted: 100.0% Logical volume lvol1 converted. lvs -a -o name,copy_percent,devices vg00 LV Copy% Devices lvol1 100.00 lvol1_mimage_0(0),lvol1_mimage_1(0),lvol1_mimage_2(0) [lvol1_mimage_0] /dev/sda1(0) [lvol1_mimage_1] /dev/sdb1(0) [lvol1_mimage_2] /dev/sdc1(0) [lvol1_mlog] /dev/sdd1(0)
8.3. Evaluating the Tools An assessment can start by using some form of an information gathering tool. When assessing the entire network, map the layout first to find the hosts that are running. Once located, examine each host individually. Focusing on these hosts requires another set of tools. Knowing which tools to use may be the most crucial step in finding vulnerabilities. Just as in any aspect of everyday life, there are many different tools that perform the same job. This concept applies to performing vulnerability assessments as well. There are tools specific to operating systems, applications, and even networks (based on the protocols used). Some tools are free; others are not. Some tools are intuitive and easy to use, while others are cryptic and poorly documented but have features that other tools do not. Finding the right tools may be a daunting task and in the end, experience counts. If possible, set up a test lab and try out as many tools as you can, noting the strengths and weaknesses of each. Review the README file or man page for the tool. Additionally, look to the Internet for more information, such as articles, step-by-step guides, or even mailing lists specific to a tool. The tools discussed below are just a small sampling of the available tools. 8.3.1. Scanning Hosts with Nmap Nmap is a popular tool included in Red Hat Enterprise Linux that can be used to determine the layout of a network. Nmap has been available for many years and is probably the most often used tool when gathering information. An excellent man page is included that provides a detailed description of its options and usage. Administrators can use Nmap on a network to find host systems and open ports on those systems. Nmap is a competent first step in vulnerability assessment. You can map out all the hosts within your network and even pass an option that allows Nmap to attempt to identify the operating system running on a particular host. Nmap is a good foundation for establishing a policy of using secure services and stopping unused services. 8.3.1.1. Using Nmap Nmap can be run from a shell prompt by typing the nmap command followed by the hostname or IP address of the machine to scan. The results of the scan (which could take up to a few minutes, depending on where the host is located) should look similar to the following: Nmap tests the most common network communication ports for listening or waiting services. This knowledge can be helpful to an administrator who wants to close down unnecessary or unused services. For more information about using Nmap, refer to the official homepage at the following URL: http://www.insecure.org/

Commands:
nmap foo.example.com
Starting nmap V. 3.50 ( www.insecure.org/nmap/ ) Interesting ports on localhost.localdomain (127.0.0.1): (The 1591 ports scanned but not shown below are in state: closed) Port State Service 22/tcp open ssh 25/tcp open smtp 111/tcp open sunrpc 443/tcp open https 515/tcp open printer 950/tcp open oftep-rpc 6000/tcp open X11 Nmap run completed -- 1 IP address (1 host up) scanned in 71.825 seconds
10.5.64. NameVirtualHost The NameVirtualHost directive associates an IP address and port number, if necessary, for any name-based virtual hosts. Name-based virtual hosting allows one Apache HTTP Server to serve different domains without using multiple IP addresses. Note Name-based virtual hosts only work with non-secure HTTP connections. If using virtual hosts with a secure server, use IP address-based virtual hosts instead. To enable name-based virtual hosting, uncomment the NameVirtualHost configuration directive and add the correct IP address. Then add additional VirtualHost containers for each virtual host as is necessary for your configuration.

Commands: