mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Overview Red Hat Trusted Application Pipeline RHTAP is a DevSecOps framework that integrates security from project inception to production. It reduces security risks in continuous integration/continuous delivery (CI/CD) pipelines by embedding security checks, ensuring artifact integrity, and enabling compliance with standards such as Supply chain Levels for Software Artifacts (SLSA). 1.1. Key features Ready-to-use templates : Start project quickly with customizable templates that include established security practices. Reduce setup time and focus on delivering secure software sooner. Secure CI/CD pipelines : Build, test, and deploy container images securely using pre-configured pipelines integrated with your Git repository. Apply security measures at every stage to reduce risks before code reaches production. Integrated security checks : Detect and address potential vulnerabilities with detailed insights to help understand the potential threats. SBOM management : Automatically generate a Software Bill of Materials (SBOM) for each pipeline. Sign attestations and maintain a clear record of component origins, ensuring traceability and compliance throughout the software life cycle. Tamper-proof artifact signing : Apply cryptographic signatures to code submissions and related artifacts. Maintain an immutable log of build and deployment activities to preserve trust and integrity. Compliance and policy enforcement : Comply with standards such as Supply chain Levels for Software Artifacts (SLSA) Level 3 and enterprise requirements. Configure approval gates, run vulnerability scans, and enforce policies so only verified, compliant artifacts move forward. 1.2. Integrated technologies RHTAP integrates with industry-leading platforms and tools: Component or Technology Description Red Hat Developer Hub (RHDH) A self-service portal that streamlines development and integrates security best practices from the get-go. Red Hat Trusted Artifact Signer (RHTAS) Enhances software integrity through signature and attestation, ensuring all artifacts are secure and authentic. Red Hat Trusted Profile Analyzer (RHTPA) Automates the creation and management of SBOMs, providing transparency and compliance in your software supply chain. Advanced Cluster Security (ACS) Automates the scanning of artifacts for vulnerabilities. OpenShift GitOps Automates application deployment and lifecycle management, ensuring consistent versions of app definitions, configurations, and environments. OpenShift Pipelines Automates the CI/CD processes with visibility and control over build, test, and deployment workflows. 1.3. Configuration options RHTAP allows flexibility in CI/CD management, source repositories, and artifact registries: Category Options CI/CD pipelines Tekton (Default) Jenkins GitHub Actions (Technology preview) Gitlab CI Note All CI pipelines except Tekton conform to SLSA Build L2. Tekton conforms to Build L3. Source repositories GitHub (Default) GitLab Bitbucket cloud Artifact registries Quay (Default) JFrog Artifactory

Commands:
5.237. perl-SOAP-Lite 5.237.1. RHBA-2012:1388 - perl-SOAP-Lite bug fix update An updated perl-SOAP-Lite package that fixes one bug is now available for Red Hat Enterprise Linux 6. SOAP::Lite is a collection of Perl modules, which provides a simple and lightweight interface to the Simple Object Access Protocol (SOAP) both on client and server side. Bug Fix BZ# 748376 XMLRPC requests could fail if the MOD_PERL environment value was defined. The standard read() function is now used instead of the sysread() function when MOD_PERL is defined. As a result, XMLRPC no longer fails in this scenario. All users of perl-SOAP-Lite are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 24. Red Hat Enterprise Linux Atomic Host 7.4.5 24.1. Atomic Host OStree update : New Tree Version: 7.4.5 (hash: 4af8e7e81f8051abc4a49dce23c8a75574abe8ad33faa5d52b59d992330d7f27) Changes since Tree Version 7.4.4 (hash: 91b59e14c4eef641f388cbc5b2cbbdd4653a89f4053d684217d9c1c9394c3dd3) Updated packages : cockpit-ostree-160-1.el7 24.2. Extras Updated packages : atomic-1.22.1-1.gitd36c015.el7 buildah-0.11-3.git49095a8.el7 cockpit-160-1.el7 container-selinux-2.42-1.gitad8f0f7.el7 docker-1.13.1-53.git774336d.el7 docker-latest-1.13.1-53.git774336d.el7 etcd-3.2.15-1.el7 gomtree-0.5.0-0.2.git16da0f8.el7 oci-register-machine-0-6.git2b44233.el7 oci-systemd-hook-0.1.15-2.gitc04483d.el7 oci-umount-2.3.3-3.gite3c9055.el7 rhel-system-roles-0.6-1.el7 * runc-1.0.0-26.rc4.dev.git9f9c962.el7 skopeo-0.1.28-1.git0270e56.el7 The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 24.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.4 Container Image (rhel7.4, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Kubernetes apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes controller-manager Container (rhel7/kubernetes-controller-mgr) Red Hat Enterprise Linux Atomic Kubernetes scheduler Container Image (rhel7/kubernetes-scheduler) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) 24.3. New Features docker and docker-latest are now the same version In RHEL Atomic Host 7.4.5, docker and docker-latest are both version 1.13.1. In RHEL Atomic Host 7.5.0, docker-latest will be available, but deprecated. In a later version of RHEL Atomic Host, docker-latest will be removed. ansible deprecated in the Extras channel Ansible and its dependencies are no longer updated through the Extras channel. For more information, see the 7.5.0 release note about Ansible removal .

Commands:
Chapter 18. Managing Access Control This chapter describes how you use Access Control Instructions (ACI) in Red Hat Directory Server to manage access to entries. 18.1. Access Control Principles When Directory Server receives a request, it uses the authentication information provided by the user in the bind operation and the ACIs defined in the directory to allow or deny access to the requested entry or attribute. The server can allow or deny permissions for actions, such as read , write , search , and compare . The permission level granted to a user depends on the authentication information provided. Access control in Directory Server enables you to set precise rules on when the ACIs are applicable: For the entire directory, a subtree, or specific entries For a specific user, all users belonging to a specific group or role, or all users in the directory For a specific location, such as an IP address, an IP range, or a DNS name. Note that load balancers can affect location-specific rules. Important Complex ACIs are difficult to read and understand. Instead of one complex ACI, you can write multiple simple rules to achieve the same effect. However, a higher number of ACIs also increases the costs of ACI processing.

Commands:
20.6. Requiring SSH for Remote Connections For SSH to be truly effective, using insecure connection protocols, such as Telnet and FTP, should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include: telnet rsh rlogin vsftpd To disable insecure connection methods to the system, use the command line program chkconfig , the ncurses-based program /usr/sbin/ntsysv , or the Services Configuration Tool ( system-config-services ) graphical application. All of these tools require root level access. For more information on runlevels and configuring services with chkconfig , /usr/sbin/ntsysv , and the Services Configuration Tool , refer to the chapter titled Controlling Access to Services in the System Administrators Guide .

Commands:
25.5.4. Using the New Syntax for rsyslog queues In the new syntax available in rsyslog 7, queues are defined inside the action() object that can be used both separately or inside a ruleset in /etc/rsyslog.conf . The format of an action queue is as follows: action(type=" action_type " queue.size=" queue_size " queue.type=" queue_type " queue.filename=" file_name ") Replace action_type with the name of the module that is to perform the action and replace queue_size with a maximum number of messages the queue can contain. For queue_type , choose disk or select from one of the in-memory queues: direct , linkedlist or fixedarray . For file_name specify only a file name, not a path. Note that if creating a new directory to hold log files, the SELinux context must be set. See Section 25.5.2, "Creating a New Directory for rsyslog Log Files" for an example. Example 25.13. Defining an Action Queue To configure the output action with an asynchronous linked-list based action queue which can hold a maximum of 10,000 messages, enter a command as follows: action(type="omfile" queue.size="10000" queue.type="linkedlist" queue.filename="logfile") The rsyslog 7 syntax for a direct action queues is as follows: The rsyslog 7 syntax for an action queue with multiple parameters can be written as follows: The default work directory, or the last work directory to be set, will be used. If required to use a different work directory, add a line as follows before the action queue: global(workDirectory=" /directory ") Example 25.14. Forwarding To a Single Server Using the New Syntax The following example is based on the procedure Procedure 25.2, "Forwarding To a Single Server" in order to show the difference between the traditional sysntax and the rsyslog 7 syntax. The omfwd plug-in is used to provide forwarding over UDP or TCP . The default is UDP . As the plug-in is built in it does not have to be loaded. Use the following configuration in /etc/rsyslog.conf or create a file with the following content in the /etc/rsyslog.d/ directory: Where: queue.type="linkedlist" enables a LinkedList in-memory queue, queue.filename defines a disk storage. The backup files are created with the example_fwd prefix, in the working directory specified by the preceding global workDirectory directive, the action.resumeRetryCount -1 setting prevents rsyslog from dropping messages when retrying to connect if server is not responding, enabled queue.saveOnShutdown="on" saves in-memory data if rsyslog shuts down, the last line forwards all received messages to the logging server, port specification is optional.

Commands:
*.* action(type="omfile" file="/var/lib/rsyslog/ log_file )
*.* action(type="omfile" queue.filename=" log_file " queue.type="linkedlist" queue.size="10000" )
*.* action(type="omfwd" queue.type="linkedlist" queue.filename="example_fwd" action.resumeRetryCount="-1" queue.saveOnShutdown="on" target="example.com" port="6514" protocol="tcp" )
Chapter 44. Capturing network packets To debug network issues and communications, you can capture network packets. The following sections provide instructions and additional information about capturing network packets. 44.1. Using xdpdump to capture network packets including packets dropped by XDP programs The xdpdump utility captures network packets. Unlike the tcpdump utility, xdpdump uses an extended Berkeley Packet Filter(eBPF) program for this task. This enables xdpdump to also capture packets dropped by Express Data Path (XDP) programs. User-space utilities, such as tcpdump , are not able to capture these dropped packages, as well as original packets modified by an XDP program. You can use xdpdump to debug XDP programs that are already attached to an interface. Therefore, the utility can capture packets before an XDP program is started and after it has finished. In the latter case, xdpdump also captures the XDP action. By default, xdpdump captures incoming packets at the entry of the XDP program. Important On other architectures than AMD and Intel 64-bit, the xdpdump utility is provided as a Technology Preview only. Technology Preview features are not supported with Red Hat production Service Level Agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These previews provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features. Note that xdpdump has no packet filter or decode capabilities. However, you can use it in combination with tcpdump for packet decoding. Prerequisites A network driver that supports XDP programs. An XDP program is loaded to the enp1s0 interface. If no program is loaded, xdpdump captures packets in a similar way tcpdump does, for backward compatibility. Procedure To capture packets on the enp1s0 interface and write them to the /root/capture.pcap file, enter: To stop capturing packets, press Ctrl + C . Additional resources xdpdump(8) man page on your system If you are a developer and you are interested in the source code of xdpdump , download and install the corresponding source RPM (SRPM) from the Red Hat Customer Portal. 44.2. Additional resources How to capture network packets with tcpdump? (Red Hat Knowledgebase)

Commands:
xdpdump -i enp1s0 -w /root/capture.pcap
Chapter 6. MTR 1.2.3 6.1. New features This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.2.3: New rules support for Camel 4.1. New rules support the migration of Java EE applications to Quarkus. 6.2. Known issues For a complete list of all known issues, see the list of MTR 1.2.3 known issues in Jira. 6.3. Resolved issues CVE-2023-1436 org.keycloak-keycloak-parent: Jettison: Uncontrolled Recursion in JSONArray A flaw in Jettison , which was utilized by MTR, triggers an infinite recursion when constructing a JSONarray from a Collection where one of the elements self-references. This flaw throws a StackOverflowError exception. (WINDUP-3772) For more details, see CVE-2023-1436 For a complete list of all issues resolved in this release, see the list of MTR 1.2.3 resolved issues in Jira.

Commands:
Part III. Managing assets in Business Central As a process administrator, you can use Business Central in Red Hat Process Automation Manager to manage assets, such as rules, business processes, and decision tables. Prerequisites Red Hat JBoss Enterprise Application Platform 7.4 is installed. For details, see Red Hat JBoss Enterprise Application Platform 7.4 Installation Guide . Red Hat Process Automation Manager is installed and configured with KIE Server. For more information see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Red Hat Process Automation Manager is running and you can log in to Business Central with the developer role. For more information, see Planning a Red Hat Process Automation Manager installation .

Commands:
Chapter 1. Introduction to Red Hat Software certification The Red Hat Software certification program ensures compatibility of your software products on Red Hat platforms. Building and certifying your products on Red Hat platforms ensures that your solutions are consistent, interoperable, and supported. Red Hat certifications give you confidence on your deployments, and that lets you focus on delivering valuable and transformative technology to your customers. The key benefits of the Red Hat Software certification program are: Build once and deploy across bare-metal, virtualized, and public and private cloud infrastructure. Take advantage of Red Hat expertise with emerging technologies, so you can make time for innovation while managing risk. Build trust and customer confidence by offering collaborative support with Red Hat and TSANet. Generate market awareness and customer demand through placement and promotion on the Red Hat Ecosystem Catalog. Use the following table to find the required software certifications available on your Red Hat platform: Table 1.1. Red Hat Software Certification Matrix Certification Platforms Application and Workloads Infrastructure and Automation Red Hat Enterprise Linux Platform Containers RPMs Others Not applicable Red Hat OpenShift Container Platform Operators Helm Charts Containers CNF CNI CSI Red Hat Ansible Automation Platform Not applicable Ansible Collection Policy Ansible Collection Workflow Red Hat OpenStack Platform Containers NFV VNF Cinder Manila Neutron

Commands:
5.209. nfs4-acl-tools 5.209.1. RHBA-2012:0783 - nfs4-acl-tools bug fix update An updated nfs4-acl-tools package that fixes one bug is now available for Red Hat Enterprise Linux 6. The nfs4-acl-tools package provides utilities for managing NFSv4 Access Control Lists (ACLs) on files and directories mounted on ACL-enabled NFSv4 file systems. Bug Fix BZ# 769862 Prior to this update, several uninitialized stack pointers were incorrectly freed. As a consequence, the "nfs4_setfacl" command failed with the error message "*** glibc detected *** nfs4_setfacl: double free or corruption (out)" if the format of the input ACL file was incorrect. This update corrects the memory handling process. Now, the nfs4_setfacl command displays a useful error message if the input file syntax is invalid. All users of nfs4-acl-tools are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. Introduction to Anaconda customization 1.1. Introduction to Anaconda Customization The Red Hat Enterprise Linux and Fedora installation program, Anaconda , brings many improvements in its most recent versions. One of these improvements is enhanced customizability. You can now write add-ons to extend the base installer functionality, and change the appearance of the graphical user interface. This document will explain how to customize the following: Boot menu - pre-configured options, color scheme and background Appearance of the graphical interface - logo, backgrounds, product name Installer functionality - add-ons which can enhance the installer by adding new Kickstart commands and new screens in the graphical and textual user interfaces Also note that this document applies only to Red Hat Enterprise Linux 8 and Fedora 17 and later. Important Procedures described in this book are written for Red Hat Enterprise Linux 8 or a similar system. On other systems, the tools and applications used (such as genisoimage for creating custom ISO images) may be different, and procedures may need to be adjusted. Support Statement Red Hat supports only customizing the Red Hat Enterprise Linux installation media and images by using Red Hat Enterprise Linux Image Builder. Alternatively, you can use Kickstart to deploy consistent systems in your infrastructure.

Commands:
4.3. Installing the Replica Packages Since the replica is an IdM server (based on the configuration of an existing server), it is installed from the IdM server packages, ipa-server . If the replica will also host DNS services, then include the bind and bind-dyndb-ldap packages. [root@server ~]# yum install ipa-server bind bind-dyndb-ldap Important Do not run the ipa-server-install script.

Commands:
yum install ipa-server bind bind-dyndb-ldap
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 Configuring firewalls and packet filters .

Commands:
Chapter 1. Support level definitions New features, services, and components go through a number of support levels before inclusion in Red Hat build of Apache Camel for Quarkus as fully supported for production use. This is to ensure the right balance between providing the enterprise stability expected of our offerings with the need to allow our customers and partners to experiment with new Red Hat build of Apache Camel for Quarkus technologies while providing feedback to help guide future development activities. Table 1.1. Red Hat build of Apache Camel for Quarkus support levels Type Description Community Support As part of Red Hat's commitment to upstream first, integration of new extensions into our Red Hat build of Apache Camel for Quarkus distribution begins in the upstream community. While these extensions have been tested and documented upstream, we have not reviewed the maturity of these extensions and they may not be formally supported by Red Hat in future product releases. Note Community extensions are listed on the extensions reference page of the Camel Quarkus community project. Technology Preview Technology Preview features provide early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. However, these features are not fully supported under Red Hat Subscription Level Agreements, may not be functionally complete, and are not intended for production use. As Red Hat considers making future iterations of Technology Preview features generally available, we will attempt to resolve any issues that customers experience when using these features. Production Support Production Support extensions are shipped in a formal Red Hat release and are fully supported. There are no documentation gaps and extensions have been tested on all supported configurations.

Commands:
Chapter 19. Annotating encrypted RBD storage classes Starting with OpenShift Data Foundation 4.14, when the OpenShift console creates a RADOS block device (RBD) storage class with encryption enabled, the annotation is set automatically. However, you need to add the annotation, cdi.kubevirt.io/clone-strategy=copy for any of the encrypted RBD storage classes that were previously created before updating to the OpenShift Data Foundation version 4.14. This enables customer data integration (CDI) to use host-assisted cloning instead of the default smart cloning. The keys used to access an encrypted volume are tied to the namespace where the volume was created. When cloning an encrypted volume to a new namespace, such as, provisioning a new OpenShift Virtualization virtual machine, a new volume must be created and the content of the source volume must then be copied into the new volume. This behavior is triggered automatically if the storage class is properly annotated.

Commands: