mtpti5iD/redhat-docs_dataset huggingface dataset:
4.5.3. Insecure Services Potentially, any network service is insecure. This is why turning unused services off is so important. Exploits for services are revealed and patched routinely, making it very important to keep packages associated with any network service updated. Refer to Chapter 3, Security Updates for more information about this issue. Some network protocols are inherently more insecure than others. These include any services which do the following things: Pass Usernames and Passwords Over a Network Unencrypted - Many older protocols, such as Telnet and FTP, do not encrypt the authentication session and should be avoided whenever possible. Pass Sensitive Data Over a Network Unencrypted - Many protocols pass data over the network unencrypted. These protocols include Telnet, FTP, HTTP, and SMTP. Many network file systems, such as NFS and SMB, also pass information over the network unencrypted. It is the user's responsibility when using these protocols to limit what type of data is transmitted. Also, remote memory dump services, like netdump , pass the contents of memory over the network unencrypted. Memory dumps can contain passwords or, even worse, database entries and other sensitive information. Other services like finger and rwhod reveal information about users of the system. Examples of inherently insecure services includes the following: rlogin rsh telnet vsftpd All remote login and shell programs ( rlogin , rsh , and telnet ) should be avoided in favor of SSH. (refer to Section 4.7, "Security Enhanced Communication Tools" for more information about sshd .) FTP is not as inherently dangerous to the security of the system as remote shells, but FTP servers must be carefully configured and monitored to avoid problems. Refer to Section 5.6, "Securing FTP" for more information on securing FTP servers. Services that should be carefully implemented and behind a firewall include: finger authd (this was called identd in RHEL releases) netdump netdump-server nfs rwhod sendmail smb (Samba) yppasswdd ypserv ypxfrd More information on securing network services is available in Chapter 5, Server Security . The section discusses tools available to set up a simple firewall.

Commands:
9.3. Import From JDBC Database You can create relational source models from your JDBC source schema data using the steps below. Note Depending the detail provided in the database connection URL information and schema, Steps 5 through 7 may not be required. In Model Explorer, right-click and then click Import... or click the File > Import... action in the toolbar or select a project, folder or model in the tree and click Import... Select the import option Teiid Designer > JDBC Database >> Source Model and click > . Select existing or connection profile from the drop-down selector or click New... button to launch the New Connection Profile dialog or Edit... to modify/change an existing connection profile prior to selection. Note The Connection Profile selection list will be populated with only JDBC Database connections. Figure 9.4. Select JDBC Source Configuration Dialog Because JDBC databases are different, special processing of your metadata to be required in order to convert datatypes or to interpret your metadata. The JDBC Metadata Processor drop-down selector will be selected automatically based on your selected connection profile. Special processors are available for DB2, ModeShape, ODBC, Oracle, PostgeSQL, SQL Server and Sybase. For all other DBs a default JDBC processor is available. After selecting a Connection Profile, enter the password (if not provided). Click > (or Finish if enabled). Figure 9.5. Select JDBC Source Configuration Dialog On the Select Database Metadata page, select the types of objects in the database to import. Click > (or Finish if enabled). Figure 9.6. Select Database Metadata Dialog On the Select Database Objects page, view the contents of the schema, or change selections. Select which database schema objects will be used to construct relational objects. Click > (or Finish if enabled). Figure 9.7. Select Database Options Dialog On the Specify Import Options page, specify desired Model Name as well as any other options used to customize the naming of your relational objects. Click Finish to complete. Figure 9.8. Specify Import Options Dialog During the Finish processing, a monitor will be displayed providing feedback on the import progress. Figure 9.9. JDBC Import Progress Dialog

Commands:
Chapter 4. Importing existing VDO volumes to LVM You can import a VDO volume that was created by the VDO manager into LVM. As a result, you can manage the volume as a logical volume using the LVM tools. Note The import operation is not reversible. After converting an existing VDO volume to LVM, accessing the VDO data is only possible using the LVM commands and the VDO manager no longer controls the volume. Prerequisites Install the VDO software. For more information, see Installing VDO . Procedure Convert an existing VDO volume created by the VDO manager into a logical volume. In the following command, replace vg-name with the volume group name, lv-name with the logical volume name, and /dev/sdg1 with the VDO device: Optional: Create a file system on the VDO LV. Optional: Mount the LVM-VDO volume. For more information, see Creating and mounting an LVM-VDO volume . Verification List your LVM devices to verify that importing the VDO volumes to LVM succeeded: Additional resources lvm_import_vdo(8) , lvmvdo(7) , and systemd.mount(5) man pages on your system

Commands:
lvm_import_vdo --name vg-name / lv-name /dev/sdg1 Convert VDO device "/dev/sdg1" to VDO LV "vg-name/lv-name"? [y|N]: Yes Stopping VDO vdo-name Converting VDO vdo-name Opening /dev/disk/by-id/scsi-36d094660575ece002291bd67517f677a-part1 exclusively Loading the VDO superblock and volume geometry Checking the VDO state Converting the UDS index Converting the VDO Conversion completed for '/dev/disk/by-id/scsi-36d094660575ece002291bd67517f677a-part1': VDO is now offset by 2097152 bytes Physical volume "/dev/sdg1" successfully created. Volume group "vg-name" successfully created WARNING: Logical volume vg-name/lv-name_vpool not zeroed. Logical volume "lv-name_vpool" created. WARNING: Converting logical volume vg-name/lv-name_vpool to VDO pool volume WITHOUT formating. WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA! Logical volume "lv-name" created. Converted vg-name/lv-name_vpool to VDO pool volume and created virtual vg-name/lv-name VDO volume.
lvs -a -o +devices LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert Devices lv-name vg-name vwi-a-v--- 25.00g lv-name_vpool 0.00 lv-name_vpool(0) lv-name_vpool vg-name dwi------- <1.82t 0.31 lv-name_vpool_vdata(0) [lv-name_vpool_vdata] vg-name Dwi-ao---- <1.82t /dev/sdg1(0)
7.137. man-pages-overrides 7.137.1. RHBA-2013:0464 - man-pages-overrides bug fix update Updated man-pages-overrides package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The man-pages-overrides package provides a collection of manual (man) pages to complement other packages or update those contained therein. Bug Fixes BZ# 806845 Prior to this update, documentation about SMBIOS on the dmidecode(8) manual page was unclear. This update fixes the information about SMBIOS on the dmidecode(8) manual page. BZ#814417 Prior to this update, description of the "-SecurityTypes" option in the TigerVNC utility was missing in the vncviewer(1) and Xvnc(1) manual pages. This update adds a description to the vncviewer(1) and Xvnc(1) manual pages. BZ# 845657 Prior to this update, the localalloc option on the numactl(8) manual page was not clearly described. This update adds a clear description of the localalloc option to the numactl(8) utility. BZ#846591 Prior to this update, some options were missing from the ipmitool(1) manual page. With this update, all options are described on the ipmitool(1) manual page. BZ# 849201 Previously, the alsaunmute(1) manual page was missing. This update adds the alsaunmute(1) manual page. BZ# 853959 Prior to this update, the "--no-tpm" option was not described in the rngd(8) manual page. This update adds a description of the "--no-tpm" option. BZ# 867332 Prior to this update, the groupmems(8) manual page was missing information about the setuid permission of the groupmems binary. This update clarifies the setuid permission in the groupmems(8) manual page. BZ# 872526 Prior to this update, the dump(8) manual page was missing information about the ext4 file system support. This update adds this information to the dump(8) manual page. Users of man-pages-overrides are advised to upgrade to this updated package, which fixes these bugs.

Commands:
B.10.7. RHBA-2011:0360 - corosync bug fix update Updated corosync packages that fix a bug are now available for Red Hat Enterprise Linux 6. [Update 18 August 2011] The channel mappings in this erratum have been updated. No changes have been made to the packages. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. Bug Fix BZ# 683592 Compared to a unicast token, certain network switches add an extra delay to the transmission of a multicast packet. Consequent to this, multicast messages may have been retransmitted, even though the message was not lost and the retransmission was therefore not necessary. This update introduces the "miss_count_const" constant that allows a user to specify the maximum number of times a message is checked for retransmission before the retransmission is performed. All users of corosync are advised to upgrade to these updated packages, which fix this bug.

Commands:
14.8.3. Suspending a Running Domain The virsh dompmsuspend domain --duration --target command will take a running domain and suspended it so it can be placed into one of three possible states (S3, S4, or a hybrid of the two). This command can take the following options: --duration - sets the duration for the state change in seconds --target - can be either mem (suspend to RAM (S3)) disk (suspend to disk (S4)) , or hybrid (hybrid suspend)

Commands:
virsh dompmsuspend rhel6 --duration 100 --target mem
Chapter 33. Desktop spice component, BZ# 1030024 Video playback on a Red Hat Enterprise Linux 7 guest with GNOME Shell is sometimes not detected as a video stream by spice-server . The video stream is therefore not compressed in such a case. kde component A companion GUI to unixODBC based on KDE is no longer maintained by upstream. There is an independent project, unixODBC-GUI-Qt , however, no stable release is available at the moment. Therefore, no supported GUI for unixODBC is available for Red Hat Enterprise Linux 7. mutter component, BZ# 861507 Support for quad-buffered OpenGL stereo visual effects in compositing window managers, such as Mutter , is missing in Red Hat Enterprise Linux 7. NVIDIA drivers currently do not support stereo visual effects when a compositing window manager is running. xorg-x11-drv-nouveau component, BZ#915857 Under some circumstances, reconnecting a monitor from one GPU port to another while the system is running can render the X server completely unresponsive to mouse and keyboard inputs. Sometimes, the monitor does not turn on in the described scenario. gobject-introspection component, BZ# 1076414 The gobject-introspection library is not available in a 32-bit multilib package. Users who wish to compile 32-bit applications that rely on GObject introspection or libraries that use it, such as GTK+ or GLib , should use the mock package to set up a build environment for their applications.

Commands:
Installation overview OpenShift Container Platform 4.18 Overview content for installing OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
oc get nodes
NAME STATUS ROLES AGE VERSION example-compute1.example.com Ready worker 13m v1.21.6+bb8d50a example-compute2.example.com Ready worker 13m v1.21.6+bb8d50a example-compute4.example.com Ready worker 14m v1.21.6+bb8d50a example-control1.example.com Ready master 52m v1.21.6+bb8d50a example-control2.example.com Ready master 55m v1.21.6+bb8d50a example-control3.example.com Ready master 55m v1.21.6+bb8d50a
oc get machines -A
NAMESPACE NAME PHASE TYPE REGION ZONE AGE openshift-machine-api example-zbbt6-master-0 Running 95m openshift-machine-api example-zbbt6-master-1 Running 95m openshift-machine-api example-zbbt6-master-2 Running 95m openshift-machine-api example-zbbt6-worker-0-25bhp Running 49m openshift-machine-api example-zbbt6-worker-0-8b4c2 Running 49m openshift-machine-api example-zbbt6-worker-0-jkbqt Running 49m openshift-machine-api example-zbbt6-worker-0-qrl5b Running 49m
capabilities: baselineCapabilitySet: v4.11 1 additionalEnabledCapabilities: 2 - CSISnapshot - Console - Storage
oc get clusteringresses.ingress.openshift.io -n openshift-ingress-operator default -o yaml
oc get deployment -n openshift-ingress
oc get network/cluster -o jsonpath='{.status.clusterNetwork[*]}'
map[cidr:10.128.0.0/14 hostPrefix:23]
oc get clusterversion version -o jsonpath='{.spec.capabilities}{"\n"}{.status.capabilities}{"\n"}'
{"additionalEnabledCapabilities":["openshift-samples"],"baselineCapabilitySet":"None"} {"enabledCapabilities":["openshift-samples"],"knownCapabilities":["CSISnapshot","Console","Insights","Storage","baremetal","marketplace","openshift-samples"]}
oc patch clusterversion version --type merge -p '{"spec":{"capabilities":{"baselineCapabilitySet":"vCurrent"}}}' 1
oc get clusterversion version -o jsonpath='{.spec.capabilities.additionalEnabledCapabilities}{"\n"}'
openshift-samples
oc patch clusterversion/version --type merge -p '{"spec":{"capabilities":{"additionalEnabledCapabilities":["openshift-samples", "marketplace"]}}}'
oc get clusterversion version -o jsonpath='{.status.conditions[?(@.type=="ImplicitlyEnabledCapabilities")]}{"\n"}'
lastTransitionTime: 2022-07-22T03:14:35Z
message: The following capabilities could not be disabled: openshift-samples
reason: CapabilitiesImplicitlyEnabled
status: True
type: ImplicitlyEnabledCapabilities
oc adm release extract --registry-config "USD{pullsecret_file}" --command=openshift-install-fips --to "USD{extract_dir}" USD{RELEASE_IMAGE}
tar -xvf openshift-install-rhel9-amd64.tar.gz
Chapter 46. Converting an uploaded spreadsheet decision table to a guided decision table in Business Central After you upload an XLS or XLSX spreadsheet decision table file to your project in Business Central, you can convert the decision table to a guided decision table that you can modify directly in Business Central. For more information about guided decision tables, see Designing a decision service using guided decision tables . Warning Guided decision tables and spreadsheet decision tables are different decision table formats that support different features. Any supported features that differ between the two decision table formats are modified or lost when you convert one decision table format to the other. Procedure In Business Central, navigate to the uploaded decision table asset that you want to convert and in the upper-right toolbar of the decision tables designer, click Convert : Figure 46.1. Convert an uploaded decision table After the conversion, the converted decision table is then available as a guided decision table asset in your project that you can modify directly in Business Central.

Commands:
Chapter 6. Administrative Tasks 6.1. Shutting Down a Virtual Machine You can turn off a virtual machine using Shutdown or Power Off . Shutdown gracefully shuts down a virtual machine. Power Off executes a hard shutdown. A graceful shutdown is usually preferable to a hard shutdown. Note If an exclamation point appears to the virtual machine, a snapshot deletion process has failed, and you may not be able to restart the machine after shutting it down. Try to delete the snapshot again and ensure that the explanation mark disappears before shutting down the virtual machine. See Deleting a snapshot for more information. Procedure Click Compute Virtual Machines and select a running virtual machine. Click Shutdown or right-click the virtual machine and select Shutdown from the pop-up menu. Optionally in the Administration Portal, enter a Reason for shutting down the virtual machine in the Shut down Virtual Machine(s) confirmation window. This allows you to provide an explanation for the shutdown, which will appear in the logs and when the virtual machine is powered on again. Note The virtual machine shutdown Reason field will only appear if it has been enabled in the cluster settings. For more information, see Explanation of Settings and Controls in the New Cluster and Edit Cluster Windows in the Administration Guide . Click OK in the Shut down Virtual Machine(s) confirmation window. If the virtual machine gracefully shuts down, the Status of the virtual machine changes to Down . If the virtual machine does not gracefully shut down, click the down arrow to Shutdown and then click Power Off to execute a hard shutdown, or right-click the virtual machine and select Power Off from the pop-up menu.

Commands:
2.3. Configuring Authentication and Role Mapping using JBoss EAP Login Modules When using Red Hat JBoss EAP log in module for querying roles from LDAP, you must implement your own mapping of Principals to Roles, as JBoss EAP uses its own custom classes. The following example demonstrates how to map a principal obtained from JBoss EAP login module to a role. It maps user principal name to a role, performing a similar action to the IdentityRoleMapper : Example 2.1. Mapping a Principal from JBoss EAP's Login Module Example 2.2. Example of JBoss EAP LDAP login module configuration Example 2.3. Example of JBoss EAP Login Module Configuration When using GSSAPI authentication, this would typically involve using LDAP for role mapping, with JBoss EAP server authenticating itself to the LDAP server via GSSAPI. For more information on how to configure this, see the JBoss EAP Administration and Configuration Guide . Important For information about how to configure JBoss EAP login modules, see the JBoss EAP Administration and Configuration Guide and see the Red Hat Directory Server Administration Guide how to configure LDAP server, and specify users and their role mapping. Report a bug

Commands:
public class SimplePrincipalGroupRoleMapper implements PrincipalRoleMapper { @Override public Set<String> principalToRoles(Principal principal) { if (principal instanceof SimpleGroup) { Enumeration<Principal> members = ((SimpleGroup) principal).members(); if (members.hasMoreElements()) { Set<String> roles = new HashSet<String>(); while (members.hasMoreElements()) { Principal innerPrincipal = members.nextElement(); if (innerPrincipal instanceof SimplePrincipal) { SimplePrincipal sp = (SimplePrincipal) innerPrincipal; roles.add(sp.getName()); } } return roles; } } return null; } }
<security-domain name="ispn-secure" cache-type="default"> <authentication> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> <module-option name="java.naming.provider.url" value="ldap://localhost:389"/> <module-option name="java.naming.security.authentication" value="simple"/> <module-option name="principalDNPrefix" value="uid="/> <module-option name="principalDNSuffix" value=",ou=People,dc=infinispan,dc=org"/> <module-option name="rolesCtxDN" value="ou=Roles,dc=infinispan,dc=org"/> <module-option name="uidAttributeID" value="member"/> <module-option name="matchOnUserDN" value="true"/> <module-option name="roleAttributeID" value="cn"/> <module-option name="roleAttributeIsDN" value="false"/> <module-option name="searchScope" value="ONELEVEL_SCOPE"/> </login-module> </authentication> </security-domain>
<security-domain name="krb-admin" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="useKeyTab" value="true"/> <module-option name="principal" value="admin@INFINISPAN.ORG"/> <module-option name="keyTab" value="USD{basedir}/keytab/admin.keytab"/> </login-module> </authentication> </security-domain>
Chapter 6. Red Hat Enterprise Linux Atomic Host 7.7.5 6.1. Atomic Host OStree update : New Tree Version: 7.7.5 (hash: fa5ed9df25ffe265b2f3504fb2711a6633d051c62a0f6a8b3d095799c1befc8b) Changes since Tree Version 7.7.4 (hash: 422dc6900aa50ce4fb23adee368890e770007a644addb0558e23cfb52d4efd26) 6.2. Extras Updated packages : docker-1.13.1-109.gitcccb291.el7_7 python-flask-0.10.1-5.el7_7 slirp4netns-0.3.0-8.el7_7 6.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.7 Container Image (rhel7.7, 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 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) Red Hat Universal Base Image 7 Container Image (rhel7/ubi7) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) Red Hat Universal Base Image 7 Minimal Container Image (rhel7/ubi7-minimal)

Commands:
Chapter 4. Image-naming conventions 4.1. Red Hat's Naming Policy Red Hat has provided a consistent naming policy for Docker-formatted images in order to provide predictability for users. Docker URLs in the V1 version of the protocol and registry format work similar to GitHub repository names. Their structure is: The implicit default registry is docker.io . This means that relative URLs, such as "redhat/rhel" resolve to docker.io/redhat/rhel . The special name "library/*" maps to direct, non-prefixed images. For instance: "docker.io/rhel". 4.2. Redirection of Requests Requests for Red Hat content are redirected from docker.io to registry.access.redhat.com . The following mappings describe this redirection: docker.io/rhel registry.access.redhat.com/rhel (alias for rhel7) docker.io/rhel7 registry.access.redhat.com/rhel7 docker.io/rhel6 registry.access.redhat.com/rhel6 docker.io/redhat/* registry.access.redhat.com/redhat/* The version of Docker that ships with Red Hat Enterprise Linux 7.2 contacts the internal Red Hat registry by default. This allows Red Hat to segment the namespace by registry. The registry content is a mapping of tagged names and does not involve any copying of content. This mapping is achieved by means of multiple symbolic links. Red Hat keeps these links up-to-date to ensure the integrity of your data. The REPO is a repository containing a number of explicitly tagged and a number of hidden layers. An 'IMAGE' is a specific layer-complete branch within a repository. Often the terms 'image' and 'repository' are used synonymously, even thought they are not the same. For instance, different images can be tagged into a single repository.

Commands:
REGISTRY[:PORT]/USER/REPO[:TAG]
function::uaddr Name function::uaddr - User space address of current running task. EXPERIMENTAL. Synopsis Arguments None General Syntax uaddr: long Description Returns the address in userspace that the current task was at when the probe occurred. When the current running task isn't a user space thread, or the address cannot be found, zero is returned. Can be used to see where the current task is combined with usymname or symdata . Often the task will be in the VDSO where it entered the kernel. FIXME - need VDSO tracking support #10080.

Commands:
function uaddr:long()