mtpti5iD/redhat-docs_dataset huggingface dataset:
8.43. device-mapper-persistent-data 8.43.1. RHBA-2014:1409 - device-mapper-persistent-data bug fix and enhancement update Updated device-mapper-persistent-data packages that fix one bug and add two enhancements are now available. The device-mapper-persistent-data packages provide device-mapper thin provisioning (thinp) tools. This update adds thin provisioning tools to support the dm-cache, as well as the dm-era functionality for change tracking to the device-mapper-persistent-data packages in Red Hat Enterprise Linux 6 as a Technology Preview. (BZ# 1038236 , BZ# 1084081 ) More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ In addition, this update fixes the following bug: Bug Fix BZ# 1035990 The thin_dump utility as well as other persistent-data tools supported only 512 B block sizes on accessed devices. Consequently, persistent-data tools could perform I/O to misaligned buffers. The underlying source code has been updated to support 4 KB block size, thus fixing this bug. This update adds thin provisioning tools to support the dm-cache, as well as the dm-era functionality for change tracking to the device-mapper-persistent-data packages in Red Hat Enterprise Linux 6 as a Technology Preview. (BZ#1038236, BZ#1084081) More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ Users of device-mapper-persistent-data are advised to upgrade to these updated packages, which fix this bug and add these enhancements.

Commands:
Chapter 129. KafkaBridgeConsumerSpec schema reference Used in: KafkaBridgeSpec Full list of KafkaBridgeConsumerSpec schema properties Configures consumer options for the Kafka Bridge as keys. The values can be one of the following JSON types: String Number Boolean Exceptions You can specify and configure the options listed in the Apache Kafka configuration documentation for consumers . However, Streams for Apache Kafka takes care of configuring and managing options related to the following, which cannot be changed: Kafka cluster bootstrap address Security (encryption, authentication, and authorization) Consumer group identifier Properties with the following prefixes cannot be set: bootstrap.servers group.id sasl. security. ssl. If the config property contains an option that cannot be changed, it is disregarded, and a warning message is logged to the Cluster Operator log file. All other supported options are forwarded to Kafka Bridge, including the following exceptions to the options configured by Streams for Apache Kafka: Any ssl configuration for supported TLS versions and cipher suites Example Kafka Bridge consumer configuration apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # ... consumer: config: auto.offset.reset: earliest enable.auto.commit: true # ... Important The Cluster Operator does not validate keys or values in the config object. If an invalid configuration is provided, the Kafka Bridge deployment might not start or might become unstable. In this case, fix the configuration so that the Cluster Operator can roll out the new configuration to all Kafka Bridge nodes. 129.1. KafkaBridgeConsumerSpec schema properties Property Property type Description config map The Kafka consumer configuration used for consumer instances created by the bridge. Properties with the following prefixes cannot be set: ssl., bootstrap.servers, group.id, sasl., security. (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols).

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # consumer: config: auto.offset.reset: earliest enable.auto.commit: true #
7.4. amanda 7.4.1. RHBA-2013:0427 - amanda bug fix update Updated amanda packages that fix one bug are now available for Red Hat Enterprise Linux 6. AMANDA, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that allows the administrator of a LAN to set up a single master backup server to back up multiple hosts to one or more tape drives or disk files. Bug Fix BZ#752096 Previously, the amandad daemon, which is required for successful running of AMANDA, was located in the amanda-client package; however, this package was not required during installation of the amanda-server package. Consequently, AMANDA did not work properly. The amanda-client package has been added to the amanda-server dependencies and AMANDA works correctly now. All AMANDA users are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. About this tutorial The tutorial includes the following steps: Deploy a MySQL database server with a simple example database to OpenShift. Apply a custom resource in AMQ Streams to automatically build a Kafka Connect container image that includes the Debezium MySQL connector plug-in. Create the Debezium MySQL connector resource to capture changes in the database. Verify the connector deployment. View the change events that the connector emits to a Kafka topic from the database. Prerequisites You are familiar with OpenShift and AMQ Streams. You have access to an OpenShift cluster on which the cluster Operator is installed. The AMQ Streams Operator is running. An Apache Kafka cluster is deployed as documented in Deploying and Managing AMQ Streams on OpenShift . You have a Red Hat Integration license. You know how to use OpenShift administration tools. The OpenShift oc CLI client is installed or you have access to the OpenShift Container Platform web console. Depending on how you intend to store the Kafka Connect build image, you must either have permission to access a container registry, or you must create an ImageStream resource on OpenShift: To store the build image in an image registry, such as Red Hat Quay.io or Docker Hub An account and permissions to create and manage images in the registry. To store the build image as a native OpenShift ImageStream An ImageStream resource is deployed to the cluster for storing new container images. You must explicitly create an ImageStream for the cluster. ImageStreams are not available by default. Additional resources: Managing image streams on OpenShift Container Platform .

Commands:
5.7.4.2. Removing Storage Removing disk space from a system is straightforward, with most of the steps being similar to the installation sequence (except, of course, in reverse): Move any data to be saved off the disk drive Modify the backup schedule so that the disk drive is no longer backed up Update the system configuration Erase the contents of the disk drive Remove the disk drive As you can see, compared to the installation process, there are a few extra steps to take. These steps are discussed in the following sections. 5.7.4.2.1. Moving Data Off the Disk Drive Should there be any data on the disk drive that must be saved, the first thing to do is to determine where the data should go. This decision depends mainly on what is going to be done with the data. For example, if the data is no longer going to be actively used, it should be archived, probably in the same manner as your system backups. This means that now is the time to consider appropriate retention periods for this final backup. Note Keep in mind that, in addition to any data retention guidelines your organization may have, there may also be legal requirements for retaining data for a certain length of time. Therefore, make sure you consult with the department that had been responsible for the data while it was still in use; they should know the appropriate retention period. On the other hand, if the data is still being used, then the data should reside on the system most appropriate for that usage. Of course, if this is the case, perhaps it would be easiest to move the data by reinstalling the disk drive on the new system. If you do this, you should make a full backup of the data before doing so -- people have dropped disk drives full of valuable data (losing everything) while doing nothing more hazardous than walking across a data center.

Commands:
Chapter 7. http 7.1. http:proxies 7.1.1. Description List the HTTP proxies 7.1.2. Syntax http:proxies [options] 7.1.3. Options Name Description --help Display this help message 7.2. http:proxy-add 7.2.1. Description Add a new HTTP proxy 7.2.2. Syntax http:proxy-add [options] url proxyTo 7.2.3. Arguments Name Description url HTTP proxy URL proxyTo HTTP location to proxy on the prefix 7.2.4. Options Name Description --help Display this help message 7.3. http:proxy-remove 7.3.1. Description Remove an existing HTTP proxy 7.3.2. Syntax http:proxy-remove [options] prefix 7.3.3. Arguments Name Description prefix The HTTP proxy prefix 7.3.4. Options Name Description --help Display this help message

Commands:
5.9.2.4. MSDOS Red Hat Enterprise Linux also supports file systems from other operating systems. As the name for the msdos file system implies, the original operating system supporting this file system was Microsoft's MS-DOS (R). As in MS-DOS, a Red Hat Enterprise Linux system accessing an msdos file system is limited to 8.3 file names. Likewise, other file attributes such as permissions and ownership cannot be changed. However, from a file interchange standpoint, the msdos file system is more than sufficient to get the job done.

Commands:
4.3.2. Creating User Passwords Within an Organization If there are a significant number of users within an organization, the system administrators have two basic options available to force the use of good passwords. They can create passwords for the user, or they can let users create their own passwords, while verifying the passwords are of acceptable quality. Creating the passwords for the users ensures that the passwords are good, but it becomes a daunting task as the organization grows. It also increases the risk of users writing their passwords down. For these reasons, most system administrators prefer to have the users create their own passwords, but actively verify that the passwords are good and, in some cases, force users to change their passwords periodically through password aging. 4.3.2.1. Forcing Strong Passwords To protect the network from intrusion it is a good idea for system administrators to verify that the passwords used within an organization are strong ones. When users are asked to create or change passwords, they can use the command line application passwd , which is Pluggable Authentication Manager ( PAM ) aware and therefore checks to see if the password is easy to crack or too short in length via the pam_cracklib.so PAM module. Since PAM is customizable, it is possible to add further password integrity checkers, such as pam_passwdqc (available from http://www.openwall.com/passwdqc/ ) or to write a new module. For a list of available PAM modules, refer to http://www.kernel.org/pub/linux/libs/pam/modules.html . For more information about PAM, refer to the chapter titled Pluggable Authentication Modules (PAM) in the Reference Guide . It should be noted, however, that the check performed on passwords at the time of their creation does not discover bad passwords as effectively as running a password cracking program against the passwords within the organization. There are many password cracking programs that run under Red Hat Enterprise Linux although none ship with the operating system. Below is a brief list of some of the more popular password cracking programs: Note None of these tools are supplied with Red Hat Enterprise Linux and are therefore not supported by Red Hat, Inc in any way. John The Ripper - A fast and flexible password cracking program. It allows the use of multiple word lists and is capable of brute-force password cracking. It is available online at http://www.openwall.com/john/ . Crack - Perhaps the most well known password cracking software, Crack is also very fast, though not as easy to use as John The Ripper . It can be found online at http://www.crypticide.com/users/alecm/ . Slurpie - Slurpie is similar to John The Ripper and Crack , but it is designed to run on multiple computers simultaneously, creating a distributed password cracking attack. It can be found along with a number of other distributed attack security evaluation tools online at http://www.ussrback.com/distributed.htm . Warning Always get authorization in writing before attempting to crack passwords within an organization.

Commands:
Chapter 22. ssh 22.1. ssh:ssh 22.1.1. Description Connects to a remote SSH server 22.1.2. Syntax ssh:ssh [options] hostname [command] 22.1.3. Arguments Name Description hostname The host name to connect to via SSH command Optional command to execute 22.1.4. Options Name Description --help Display this help message -P, --password The password for remote login -p, --port The port to use for SSH connection -q Quiet Mode. Do not ask for confirmations -r, --retries retry connection establishment (up to attempts times) -l, --username The user name for remote login -k, --keyfile The private keyFile location when using key login, need have BouncyCastle registered as security provider using this flag 22.2. ssh:sshd 22.2.1. Description Creates a SSH server 22.2.2. Syntax ssh:sshd [options] 22.2.3. Options Name Description --help Display this help message -b, --background The service will run in the background -p, --port The port to setup the SSH server -i, --idle-timeout The session idle timeout in milliseconds -w, --welcome-banner The welcome banner to display when logging in -n, --nio-workers The number of NIO worker threads to use

Commands:
4.11. audit 4.11.1. RHBA-2011:1739 - audit bug fix and enhancement update Updated audit packages that fix various bugs and add several enhancements are now available for Red Hat Enterprise Linux 6. The audit packages contain the user space utilities for storing and searching the audit records which have been generated by the audit subsystem in the Linux 2.6 kernel. The audit package has been upgraded to upstream version 2.1.3, which provides a number of bug fixes and enhancements over the version. (BZ# 731723 ) Bug Fixes BZ# 715279 Previously, the audit daemon was logging messages even when configured to ignore "disk full" and "disk error" actions. With this update, audit now does nothing if it is set to ignore these actions, and no messages are logged in the described scenario. BZ# 715315 Previously, the Audit remote logging client received a "disk error" event instead of "disk full" event from a server when the server's disk space ran out. This bug has been fixed and the logging client now returns the correct event in the described scenario. BZ# 748124 Prior to this update, the audit system was identifying the accept4() system call as the now deprecated paccept() system call. Now, the code has been fixed and audit uses the correct identifier for the accept4() system call. BZ# 709345 Previously, the "auditctl -l" command returned 0 even if it failed because of dropped capabilities. This bug has been fixed and a non-zero value is now returned if the operation is not permitted. BZ# 728475 When Kerberos support was disabled, some configuration options in the audisp-remote.conf file related to Kerberos 5 generated warning messages about GSSAPI support during boot. With this update, the options are now commented out in the described scenario and the messages are no longer returned. BZ# 700005 On i386 and IBM System z architectures, the "autrace -r /bin/ls" command returned error messages even though all relevant rules were added correctly. This bug has been fixed and no error messages about sending add rule data requests are now returned in the described scenario. All audit users are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.373. Red Hat Enterprise Linux 6.2 Extended Update Support 6-Month Notice 4.373.1. RHSA-2013:1001 - Low: Red Hat Enterprise Linux 6.2 Extended Update Support 6-Month Notice This is the 6-Month notification for the retirement of Red Hat Enterprise Linux 6.2 Extended Update Support (EUS). In accordance with the Red Hat Enterprise Linux Errata Support Policy, Extended Update Support for Red Hat Enterprise Linux 6.2 will be retired on December 31, 2013, and support will no longer be provided. Accordingly, Red Hat will no longer provide updated packages, including critical impact security patches or urgent priority bug fixes, for Red Hat Enterprise Linux 6.2 EUS after that date. In addition, after December 31, 2013, technical support through Red Hat's Global Support Services will no longer be provided. Note: This notification applies only to those customers subscribed to the Extended Update Support (EUS) channel for Red Hat Enterprise Linux 6.2. We encourage customers to plan their migration from Red Hat Enterprise Linux 6.2 to a more recent version of Red Hat Enterprise Linux 6. As a benefit of the Red Hat subscription model, customers can use their active subscriptions to entitle any system on a currently supported Red Hat Enterprise Linux 6 release (6.3, or 6.4, for which EUS is available). Details of the Red Hat Enterprise Linux life cycle can be found here: https://access.redhat.com/support/policy/updates/errata/

Commands:
C.19. StateTransferManager org.infinispan.statetransfer.StateTransferManager The StateTransferManager component handles state transfer in Red Hat JBoss Data Grid. Note The StateTransferManager component is only available in clustered mode. Table C.30. Attributes Name Description Type Writable joinComplete If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. boolean No stateTransferInProgress Checks whether there is a pending inbound state transfer on this cluster member. boolean No Report a bug

Commands:
5.5. Displaying and Modifying the Attribute List By default, the Referential Integrity plug-in is set up to check for and update the member , uniquemember , owner , and seeAlso attributes. You can add or delete attributes to be updated using the command line or the web console. Note Attributes set in the Referential Integrity plug-in's parameter list, must have equality indexing on all databases. Otherwise, the plug-in scans every entry of the database for matching the deleted or modified DN. This can have a significant performance impact. For details about checking and creating indexes, see Section 13.2, "Creating Standard Indexes" . 5.5.1. Displaying the Attribute List Using the Command Line To display the attribute list using the command line: 5.5.2. Displaying the Attribute List Using the Web Console To display the attribute list using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Open the Plugins menu. Select the Referential Integrity plug-in. See the Membership Attribute field for the list of attributes. 5.5.3. Configuring the Attribute List Using the Command Line To update the attribute list using the command line: Optionally, display the current list of attributes. See Section 5.5.1, "Displaying the Attribute List Using the Command Line" . Update the attribute list: To set an attribute list that should be checked and updated by the plug-in: To delete all attributes that should no longer be checked and updated by the plug-in: Restart the instance: 5.5.4. Configuring the Attribute List Using the Web Console To update the attribute list using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Open the Plugins menu. Select the Referential Integrity plug-in. Update the Membership Attribute field to set the attributes. To add an attribute, enter the name into the Membership Attribute field. To remove an attribute, press the X button right to the attribute's name in the Membership Attribute field. Press Save Config .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com plugin referential-integrity show
dsconf -D "cn=Directory Manager" ldap://server.example.com plugin referential-integrity set --membership-attr attribute_name_1 attribute_name_2
dsconf -D "cn=Directory Manager" ldap://server.example.com plugin referential-integrity set --membership-attr delete
dsctl instance_name restart
8.34. efibootmgr 8.34.1. RHBA-2013:1687 - efibootmgr bug fix update Updated efibootmgr packages that fix one bug are now available for Red Hat Enterprise Linux 6. The efibootmgr utility is responsible for the boot loader installation on Unified Extensible Firmware Interface (UEFI) systems. Bug Fix BZ# 924892 Previously, when an invalid value was passed to the "efibootmgr -o" command, the command did not recognize the problem and passed the incorrect value to other functions. This could have lead to several complications such as commands becoming unresponsive. With this update, efibootmgr has been modified to test for invalid input. As a result, an error message is displayed in the aforementioned scenario. Users of efibootmgr are advised to upgrade to these updated packages, which fix this bug.

Commands:
function::symdata Name function::symdata - Return the kernel symbol and module offset for the address Synopsis Arguments addr The address to translate Description Returns the (function) symbol name associated with the given address if known, the offset from the start and size of the symbol, plus module name (between brackets). If symbol is unknown, but module is known, the offset inside the module, plus the size of the module is added. If any element is not known it will be omitted and if the symbol name is unknown it will return the hex string for the given address.

Commands:
symdata:string(addr:long)
Chapter 22. Post-installation security hardening RHEL is designed with robust security features enabled by default. However, you can enhance its security further through additional hardening measures. For more information about: Installing security updates and displaying additional details about the updates to keep your RHEL systems secured against newly discovered threats and vulnerabilities, see Managing and monitoring security updates . Processes and practices for securing RHEL servers and workstations against local and remote intrusion, exploitation, and malicious activity, see Security hardening . Control how users and processes interact with the files on the system or control which users can perform which actions by mapping them to specific SELinux confined users, see Using SELinux . Tools and techniques to improve the security of your networks and lower the risks of data breaches and intrusions, see Securing networks . Packet filters, such as firewalls, that use rules to control incoming, outgoing, and forwarded network traffic, see Using and configuring firewalld and Getting started with nftables .

Commands: