mtpti5iD/redhat-docs_dataset huggingface dataset:
Installation Guide Red Hat CodeReady Workspaces 2.15 Installing Red Hat CodeReady Workspaces 2.15 Robert Kratky rkratky@redhat.com Fabrice Flore-Thebault ffloreth@redhat.com Jana Vrbkova jvrbkova@redhat.com Max Leonov mleonov@redhat.com Red Hat Developer Group Documentation Team devtools-docs@redhat.com

Commands:
Getting started with .NET on RHEL 9 .NET 9.0 Installing and running .NET 9.0 on RHEL 9 Red Hat Customer Content Services

Commands:
sudo dnf install dotnet-sdk-9.0 -y
dotnet --info
dotnet new console --output my-app
dotnet run --project my-app
Hello World!
dotnet publish my-app -f net9.0
dotnet publish my-app -f net9.0 -r rhel.9- architecture --self-contained false
dotnet new mvc --output mvc_runtime_example
dotnet publish mvc_runtime_example -f net9.0 /p:PublishProfile=DefaultContainer /p:ContainerBaseImage=registry.access.redhat.com/ubi8/dotnet-90-runtime:latest
podman run -rm -p8080:8080 mvc_runtime_example
xdg-open http://127.0.0.1:8080
B.22. flash-plugin B.22.1. RHSA-2010:0867 - Critical: flash-plugin security update An updated Adobe Flash Player package that fixes multiple security issues is now available for Red Hat Enterprise Linux 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The flash-plugin package contains a Mozilla Firefox compatible Adobe Flash Player web browser plug-in. CVE-2010-3639 , CVE-2010-3640 , CVE-2010-3641 , CVE-2010-3642 , CVE-2010-3643 , CVE-2010-3644 , CVE-2010-3645 , CVE-2010-3646 , CVE-2010-3647 , CVE-2010-3648 , CVE-2010-3649 , CVE-2010-3650 , CVE-2010-3652 , CVE-2010-3654 This update fixes multiple vulnerabilities in Adobe Flash Player. These vulnerabilities are detailed on the Adobe security page APSB10-26 . Multiple security flaws were found in the way flash-plugin displayed certain SWF content. An attacker could use these flaws to create a specially-crafted SWF file that would cause flash-plugin to crash or, potentially, execute arbitrary code when the victim loaded a page containing the specially-crafted SWF content. CVE-2010-3636 An input validation flaw was discovered in flash-plugin. Certain server encodings could lead to a bypass of cross-domain policy file restrictions, possibly leading to cross-domain information disclosure. During testing, it was discovered that there were regressions with Flash Player on certain sites, such as fullscreen playback on YouTube. Despite these regressions, we feel these security flaws are serious enough to update the package with what Adobe has provided. All users of Adobe Flash Player should install this updated package, which upgrades Flash Player to version 10.1.102.64.

Commands:
Chapter 1. Introduction For organisations running SAP production applications, it is essential to ensure the highest possible uptime for their mission critical applications by deploying them in a highly available configuration. With Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications, Red Hat provides such customers with a set of solutions to set up highly available SAP environments on top of the industry leading Red Hat Enterprise Linux High Availability cluster framework. The Red Hat Enterprise Linux High Availability Add-On provides all the necessary packages for configuring a pacemaker-based cluster that provides reliability, scalability, and availability to critical production services. On top of this, the Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications also allow for setup and configuration of highly available SAP HANA, S/4HANA and NetWeaver based SAP Applications, providing a standard-based approach to reducing planned and unplanned downtime in the corresponding SAP environment.

Commands:
Chapter 1. Interactively selecting a system-wide Red Hat build of OpenJDK version on RHEL If you have multiple versions of Red Hat build of OpenJDK installed on RHEL, you can interactively select the default Red Hat build of OpenJDK version to use system-wide. Note If you do not have root privileges, you can select an Red Hat build of OpenJDK version by configuring the JAVA_HOME environment variable. Prerequisites You must have root privileges on the system. Multiple versions of Red Hat build of OpenJDK were installed using the yum package manager. Procedure View the Red Hat build of OpenJDK versions installed on the system. USD yum list installed "java*" A list of installed Java packages appears. Display the Red Hat build of OpenJDK versions that can be used for a specific java command and select the one to use: The current system-wide Red Hat build of OpenJDK version is marked with an asterisk. The current Red Hat build of OpenJDK version for the specified java command is marked with a plus sign. Press Enter to keep the current selection or enter the Selection number of the Red Hat build of OpenJDK version you want to select followed by the Enter key. The default Red Hat build of OpenJDK version for the system is the selected version. Verify that the chosen binary is selected. Note This procedure configures the java command. Then javac command can be set up in a similar way, but it operates independently. If you have Red Hat build of OpenJDK installed, alternatives provides more possible selections. In particular, the javac master alternative switches many binaries provided by the -devel sub-package. Even if you have Red Hat build of OpenJDK installed, java (and other JRE masters) and javac (and other Red Hat build of OpenJDK masters) still operate separately, so you can have different selections for JRE and JDK. The alternatives --config java command affects the jre and its associated slaves. If you want to change the Java , use the javac alternatives command. The --config javac utility configures the SDK and related slaves. To see all possible masters, use alternatives --list and check all of the java , javac , jre , and sdk masters.

Commands:
Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.242.b08-0.el8_1 @rhel-8-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.242.b08-0.el8_1 @rhel-8-appstream-rpms java-11-openjdk.x86_64 1:11.0.6.10-0.el8_1 @rhel-8-appstream-rpms java-11-openjdk-headless.x86_64 1:11.0.6.10-0.el8_1 @rhel-8-appstream-rpms javapackages-filesystem.noarch 5.3.0-1.module+el8+2447+6f56d9a6 @rhel-8-appstream-rpms
sudo alternatives --config java There are 2 programs which provide 'java'. Selection Command ----------------------------------------------- *+ 1 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el8_1.x86_64/jre/bin/java) 2 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.6.10-0.el8_1.x86_64/bin/java) Enter to keep the current selection[+], or type selection number: 1
java -version openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
8.185. rpmlint 8.185.1. RHBA-2013:0948 - rpmlint bug fix update Updated rpmlint packages that fix two bugs are now available. Rpmlint is a tool for checking common errors in rpm packages. It can be used to test individual packages and specific files before uploading or to check an entire distribution. By default all applicable checks are processed but specific checks can be performed by using command line parameters. Bug Fixes BZ# 663082 Previously, an incorrect rule in rpmlint caused it to report a "missing-lsb-keyword Default-Stop" error message for services that did not start by default in any run level. This update corrects the rule in rpmlint, and error messages no longer occur in the described scenario. BZ# 958038 When a package had a UTF-8 encoding error in the description, or the description was encoded in a different character set, then rpmlint terminated unexpectedly with a segmentation fault. With this update, rmplint returns an error message that the description has incorrectly encoded UTF-8 data (tag-not-utf8 error), and crashes no longer occur in the described scenario. Users of rpmlint are advised to upgrade to these updated packages, which fix these bugs.

Commands:
18.12.10.10. TCP/UDP/SCTP over IPV6 Protocol ID: tcp-ipv6, udp-ipv6, sctp-ipv6 The chain parameter is ignored for this type of traffic and should either be omitted or set to root. Table 18.12. TCP, UDP, SCTP over IPv6 protocol types Attribute Name Datatype Definition srcmacaddr MAC_ADDR MAC address of sender srcipaddr IP_ADDR Source IP address srcipmask IP_MASK Mask applied to source IP address dstipaddr IP_ADDR Destination IP address dstipmask IP_MASK Mask applied to destination IP address srcipfrom IP_ADDR start of range of source IP address scripto IP_ADDR end of range of source IP address dstipfrom IP_ADDR Start of range of destination IP address dstipto IP_ADDR End of range of destination IP address srcportstart UINT16 Start of range of valid source ports srcportend UINT16 End of range of valid source ports dstportstart UINT16 Start of range of valid destination ports dstportend UINT16 End of range of valid destination ports comment STRING text string up to 256 characters state STRING comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE ipset STRING The name of an IPSet managed outside of libvirt ipsetflags IPSETFLAGS flags for the IPSet; requires ipset attribute

Commands:
4.3. Clustering and High Availability luci support for fence_sanlock The luci tool now supports the sanlock fence agent as a Technology Preview. The agent is available in the luci's list of agents. Package: luci-0.26.0-48 Recovering a node via a hardware watchdog device New fence_sanlock agent and checkquorum.wdmd, included in Red Hat Enterprise Linux 6.4 as a Technology Preview, provide new mechanisms to trigger the recovery of a node via a hardware watchdog device. Tutorials on how to enable this Technology Preview will be available at https://fedorahosted.org/cluster/wiki/HomePage Note that SELinux in enforcing mode is currently not supported. Package: cluster-3.0.12.1-59 keepalived The keepalived package has been included as a Technology Preview, starting with Red Hat Enterprise Linux 6.4. The keepalived package provides simple and robust facilities for load-balancing and high-availability. The load-balancing framework relies on the well-know and widely used Linux Virtual Server kernel module providing Layer4 network load-balancing. The keepalived daemon implements a set of health checkers to load-balanced server pools according to their state. The keepalived daemon also implements the Virtual Router Redundancy Protocol (VRRP), allowing router or director failover to achieve high availability. Package: keepalived-1.2.7-3 HAProxy HAProxy is a stand-alone, layer-7, high-performance network load balancer for TCP and HTTP-based applications which can perform various types of scheduling based on the content of the HTTP requests. The haproxy package is included as a Technology Preview, starting with Red Hat Enterprise Linux 6.4. Package: haproxy-1.4.24-2

Commands:
8. Resolved Issues 8.1. All Architectures Bugzilla #452919 Previously, if the Red Hat Network applet was used to re-register the client to a different Red Hat Satellite Server , the applet would continue to show updates that had been available on the server, even if they were not available on the current server. The /etc/sysconfig/rhn/rhn-applet would not change to reflect the details of the new server. The version of the applet provided with this update associates a cache of updates with a server url, and therefore ensure that the updates displayed to the user are actually available. This version can also detect when its configuration file has changed. If such a change is detected, the applet will automatically reload the configuration variables and create new server connections. Bugzilla #454690 On some SGI Altix systems that feature the IOC4 multi-function device, you may encounter problems when using attached IDE devices (such as CD-ROM drives). This is caused by a bug in the sgiioc4 IDE driver, which prevents some devices from being detected properly on system boot. You can work around this bug by manually loading the driver, which in turn allows attached IDE devices to be detected properly. To do so, run the following command as root: /sbin/modprobe sgiioc4 Bugzilla #454690 sysreport.legacy used USDHOME as its root directory. In case this environment variable did not exist or the directory it referred to was not writable, sysreport.legacy could not generate its report and would exit with the message Cannot make temp dir . Sysreport.legacy now uses a randomly created directory as its root directory and therefore can generate a report even on a system without a usable USDHOME . Bugzilla #476767 The automount daemon used fixed size buffer of 128 bytes long to receive information from the SIOCGIFCONF ioctl about local interfaces when testing for the proximity of a host corresponding to a given mount. Since the details of each interface are 40 bytes long, the daemon could receive information on no more than three local interfaces. If the host corresponding to the mount had an address that was local but did not correspond to one of the three interfaces the proximity would be classified incorrectly. The automount daemon now dynamically allocates a buffer, ensuring that it is large enough to contain information on all interfaces on the system providing the ability to correctly detect proximity of a host given for an NFS mount. Bugzilla #465237 Automount map entries that refer to multiple hosts in the mount location (replicated mount), the automount daemon probes a list of remote hosts for their proximity and NFS version. If hosts fail to respond, they are removed from the list. If no remote hosts reply at all, the list may become empty. Previously, the daemon did not check if the list was empty following the initial probe which would lead to a segmentation fault (by dereferencing a NULL pointer). This check has been added. Bugzilla #444942 the ttfonts-zh_CN package formerly included the Zhong Yi Song TrueType font. The

Commands:
Chapter 3. Prerequisites Before you can install and register Red Hat Satellite and Capsule, you must set up accounts with Amazon Web Services (AWS) and create and start Red Hat Enterprise Linux instances on AWS. 3.1. Amazon Web Service Assumptions To use this guide, you must have a working knowledge of the following aspects of Amazon Web Services: Creating and accessing Red Hat Enterprise Linux images in AWS Editing network access in AWS Security Creating EC2 instances and how to create EBS volumes Launching instances Importing and exporting virtual machines in AWS Using AWS Direct Connect To install Satellite in an AWS environment, you must ensure that your AWS set up meets the System Requirements in Installing Satellite Server in a Connected Network Environment . To install Capsule in an AWS environment, you must ensure that your AWS set up meets the System Requirements in Installing Capsule Server . For more information about Amazon Web Services and terminology, see Amazon Elastic Compute Cloud Documentation . For more information about Amazon Web Services Direct Connect, see What is AWS Direct Connect? 3.2. Red Hat Cloud prerequisites To use this guide, you must complete the following steps: Register with Red Hat Cloud Access. Migrate any Red Hat subscriptions that you want to use. Create an AWS instance and deploy a Red Hat Enterprise Linux virtual machine to the instance. Ensure that your subscriptions are eligible for transfer to Red Hat Cloud. For more information, see Red Hat Cloud Access Program Details . For more information about deploying Red Hat Enterprise Linux in AWS, see How to Locate Red Hat Cloud Access Gold Images on AWS EC2 . 3.3. Red Hat Satellite-specific prerequisites Ensure that the Amazon EC2 instance type meets or exceeds the System Requirements in Installing Satellite Server in a Connected Network Environment . For the best performance, use an AWS storage optimized instance . Use Storage Requirements in Installing Satellite Server in a Connected Network Environment to understand and assign the correct storage to your AWS EBS volumes. Store the synced content on an EBS volume that is separate to the boot volume. Mount the synced content EBS volume separately in the operating system. Optional: store other data on a separate EBS volume. If you want Satellite Server and Capsule Server to communicate using external DNS hostnames, open the required ports for communication in the AWS Security Group that is associated with the instance. 3.4. Preparing for the Red Hat Satellite Installation In your AWS environment, complete the following steps: Launch an EC2 instance of a Red Hat Enterprise Linux AMI. Connect to the newly created instance. If you use a Red Hat Gold Image, remove the RHUI client and set the enabled parameter in the product-id.conf to 1 .

Commands:
yum remove -y rh-amazon-rhui-client* yum clean all cat << EOF > /etc/yum/pluginconf.d/product-id.conf > [main] > enabled=1 > EOF
Chapter 3. Post-deployment IPv6 operations After you deploy the overcloud with IPv6 networking, you must perform some additional configuration. Prerequisites A successful undercloud installation. For more information, see Installing director on the undercloud . A successful overcloud deployment. For more information, see Creating a basic overcloud with CLI tools . 3.1. Creating an IPv6 project network on the overcloud The overcloud requires an IPv6-based Project network for instances. Source the overcloudrc file and create an initial Project network in neutron . Prerequisites A successful undercloud installation. For more information, see Installing director on the undercloud . A successful overcloud deployment. For more information, see Creating a basic overcloud with CLI tools . Your network supports IPv6-native VLANs as well as IPv4-native VLANs. Procedure Source the overcloud credentials file: Create a network and subnet: This creates a basic neutron network called default . Verification steps Verify that the network was created successfully: 3.2. Creating an IPv6 public network on the overcloud After you configure the node interfaces to use the External network, you must create this network on the overcloud to enable network access. Prerequisites A successful undercloud installation. For more information, see Installing director on the undercloud . A successful overcloud deployment. For more information, see Creating a basic overcloud with CLI tools . Your network supports IPv6-native VLANs as well as IPv4-native VLANs. Procedure Create an external network and subnet: This command creates a network called public that provides an allocation pool of over 65000 IPv6 addresses for our instances. Create a router to route instance traffic to the External network.

Commands:
source ~/overcloudrc
openstack network create default --external --provider-physical-network datacentre --provider-network-type vlan --provider-segment 101 openstack subnet create default --subnet-range 2001:db8:fd00:6000::/64 --ipv6-address-mode slaac --ipv6-ra-mode slaac --ip-version 6 --network default
openstack network list openstack subnet list
openstack network create public --external --provider-physical-network datacentre --provider-network-type vlan --provider-segment 100 openstack subnet create public --network public --subnet-range 2001:db8:0:2::/64 --ip-version 6 --gateway 2001:db8::1 --allocation-pool start=2001:db8:0:2::2,end=2001:db8:0:2::ffff --ipv6-address-mode slaac --ipv6-ra-mode slaac
openstack router create public-router openstack router set public-router --external-gateway public
Chapter 3. Bug fixes In this release of Red Hat Trusted Profile Analyzer (RHTPA), we fixed the following bugs. In addition to these fixes, we list the descriptions of previously known issues found in earlier versions that we fixed. Fixed an inconsistency when a CVE has many CVSS scores Before this update, vulnerabilities with many Common Vulnerability Scoring System (CVSS) scores were inconsistently displayed when applying a filter. This was happening because the first CVSS score ordered the initial list of vulnerabilities, but the second score reordered the same list when applying a filter giving an inconsistent list of vulnerabilities. With this release, we fixed this order inconsistency by always applying the highest score when ordering the list of vulnerabilities, even when applying a filter. This gives consistency to the vulnerabilities list. Changed the strategy type for deploying the spog-api and the collectorist-api in OpenShift Before this update, the default strategy type for deploying the spog-api and the collectorist-api in OpenShift was a rolling strategy. Using the rolling strategy when deploying these 2 APIs mounts a volume with a ReadWriteOnce policy. This causes the pods to fail when redeploying the RHTPA application, because the rolling strategy does not scale down, and the volume is in use by the existing pods. With this release, we changed the default strategy from rolling to recreate for the spog-api and the collectorist-api pods. Vulnerability count mismatch Before this update, there is a vulnerability count mismatch between the Common Vulnerability and Exposures (CVE) panel and the Software Bill of Materials (SBOM) dashboard. With this release, we fixed the vulnerability count mismatch between the CVE panel and the SBOM dashboard. Duplicate SBOMs displayed in the RHTPA console We fixed a bug when retrieving data from the Graph for Understanding Artifact Composition (GUAC) engine by implementing a proper identification for packages that use a hash within software bill of materials (SBOM) documents. This fix eliminates the showing of any duplicate SBOMs when referring to the same SBOM. Errors with cyclical dependencies within SBOM documents Some software bill of materials (SBOM) documents contain cyclical dependencies for packages, which was causing errors with the expected data. We fixed a bug with the Graph for Understanding Artifact Composition (GUAC) engine, so the graph is properly traversed from a package to the product it belongs to. With this update, the package details page reports the correct product association. SBOM data does not load properly when uploading a large SBOM Before this update, when uploading a large software bill of materials (SBOM) documents, for example an SBOM that includes 50,000 packages, the RHTPA dashboard does not load properly. With this release, we fixed an issue with Keycloak's access token expiring before the SBOM can finish uploading its data. Uploading large SBOM document work as expected and display properly in the RHTPA dashboard.

Commands: