You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual apt upgrade command.
118
+
3.To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual apt upgrade command.
@@ -503,7 +503,7 @@ sh install-python-els-repo.sh --license-key XXX-XXXXXXXXXXXX
503
503
```
504
504
3. Verify that the installation was successful.
505
505
506
-
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual yum upgrade command.
506
+
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual yum upgrade command.
507
507
```
508
508
yum info python2
509
509
@@ -525,7 +525,7 @@ Description : Python 2 is an old version of the language that is incompatible
525
525
```
526
526
yum install python2 --enablerepo crb
527
527
```
528
-
Once installed, you can use python2 in the usual way.
528
+
5. Once installed, you can use python2 in the usual way.
529
529
```python
530
530
$ python2
531
531
Python 2.7.18 (default, Jun 30 2022, 00:00:00)
@@ -538,15 +538,15 @@ Hello, World!
538
538
### Installation instructions of a local mirror
539
539
540
540
We provide the ability to create local mirrors of Python for ELS updates.
541
-
To obtain the access to the local mirroring, provide your External IP address to your Account Manager or send it to [[email protected]](mailto:[email protected]).
541
+
*To obtain the access to the local mirroring, provide your External IP address to your Account Manager or send it to [[email protected]](mailto:[email protected]).
542
542
543
-
To create a local mirror of the repository with security updates via `rsync`, use the following:
543
+
*To create a local mirror of the repository with security updates via `rsync`, use the following:
544
544
545
545
```
546
546
rsync://repo.cloudlinux.com/PYTHON_ELS/
547
547
```
548
548
549
-
Example of creating a local mirror for all supported OS versions:
549
+
*Example of creating a local mirror for all supported OS versions:
@@ -597,7 +597,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
597
597
-**Low-severity CVEs:** Patches provided within 90 days
598
598
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
599
599
600
-
### **Incident Reporting and Response Timeframe**
600
+
### Incident Reporting and Response Timeframe
601
601
602
602
Customers can report vulnerabilities by submitting a ticket through the TuxCare Support Portal <https://tuxcare.com/support-portal/>. TuxCare commits to providing an initial response to any reported issue within 3 days.
603
603
@@ -637,7 +637,7 @@ You need username and password in order to use TuxCare ELS Spring repository. An
637
637
638
638
**Maven**
639
639
640
-
If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
640
+
*If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
641
641
642
642
```
643
643
<?xml version="1.0" encoding="UTF-8"?>
@@ -652,16 +652,16 @@ If you are using Maven as your build automation tool, you will need to make chan
652
652
</settings>
653
653
```
654
654
655
-
Set your credentials via the following enviromnent variables:
655
+
*Set your credentials via the following environment variables:
656
656
657
657
```
658
658
export USERNAME=your-username
659
659
export PASSWORD=your-password
660
660
```
661
661
662
-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials).
662
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
663
663
664
-
You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
664
+
*You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
665
665
666
666
```
667
667
<repositories>
@@ -672,11 +672,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
672
672
</repositories>
673
673
```
674
674
675
-
An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the enviromnet variables.
675
+
*An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the environment variables.
676
676
677
677
**Gradle**
678
678
679
-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
679
+
*If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
680
680
681
681
```
682
682
repositories {
@@ -690,16 +690,16 @@ If you are using Gradle as your build automation tool, make sure to include the
690
690
}
691
691
```
692
692
693
-
Set your credentials via the following enviromnent variables:
693
+
*Set your credentials via the following environment variables:
694
694
695
695
```
696
696
export ORG_GRADLE_PROJECT_USERNAME=your-username
697
697
export ORG_GRADLE_PROJECT_PASSWORD=your-password
698
698
```
699
699
700
-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials).
700
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
701
701
702
-
An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the enviromnet variables.
702
+
*An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the environment variables.
703
703
704
704
### Verification
705
705
@@ -1678,7 +1678,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
1678
1678
-**Low-severity CVEs:** Patches provided within 90 days
1679
1679
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
1680
1680
1681
-
### **Incident Reporting and Response Timeframe**
1681
+
### Incident Reporting and Response Timeframe
1682
1682
1683
1683
Customers can report vulnerabilities by submitting a ticket through the TuxCare Support Portal <https://tuxcare.com/support-portal/>. TuxCare commits to providing an initial response to any reported issue within 3 days.
1684
1684
@@ -1710,13 +1710,13 @@ This guide outlines the steps needed to integrate the TuxCare ELS for Apache Tom
1710
1710
### Steps
1711
1711
1712
1712
### Step 1: Get user credentials
1713
-
You need username and password in order to use TuxCare ELS Apache Tomcat repository. Anonymous access is disabled. To receive username and password please contact [email protected]
1713
+
You need username and password in order to use TuxCare ELS Apache Tomcat repository. Anonymous access is disabled. To receive username and password please contact [[email protected]](mailto:[email protected]).
1714
1714
1715
1715
### Step 2: Create or Modify Your Build Tool Settings
1716
1716
1717
1717
**Maven**
1718
1718
1719
-
If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
1719
+
*If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
1720
1720
1721
1721
```
1722
1722
<?xml version="1.0" encoding="UTF-8"?>
@@ -1731,16 +1731,16 @@ If you are using Maven as your build automation tool, you will need to make chan
1731
1731
</settings>
1732
1732
```
1733
1733
1734
-
Set your credentials via the following enviromnent variables:
1734
+
*Set your credentials via the following environment variables:
1735
1735
1736
1736
```
1737
1737
export USERNAME=your-username
1738
1738
export PASSWORD=your-password
1739
1739
```
1740
1740
1741
-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials).
1741
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
1742
1742
1743
-
You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
1743
+
*You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
1744
1744
1745
1745
```
1746
1746
<repositories>
@@ -1751,11 +1751,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
1751
1751
</repositories>
1752
1752
```
1753
1753
1754
-
An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the enviromnet variables.
1754
+
*An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the environment variables.
1755
1755
1756
1756
**Gradle**
1757
1757
1758
-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
1758
+
*If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
1759
1759
1760
1760
```
1761
1761
repositories {
@@ -1769,16 +1769,16 @@ If you are using Gradle as your build automation tool, make sure to include the
1769
1769
}
1770
1770
```
1771
1771
1772
-
Set your credentials via the following enviromnent variables:
1772
+
*Set your credentials via the following environment variables:
1773
1773
1774
1774
```
1775
1775
export ORG_GRADLE_PROJECT_USERNAME=your-username
1776
1776
export ORG_GRADLE_PROJECT_PASSWORD=your-password
1777
1777
```
1778
1778
1779
-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials).
1779
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
1780
1780
1781
-
An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the enviromnet variables.
1781
+
*An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the environment variables.
1782
1782
1783
1783
### Verification
1784
1784
@@ -2023,7 +2023,7 @@ The following commands are useful for managing and troubleshooting .NET installa
2023
2023
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
2024
2024
* Click on each entry and select **Uninstall**.
2025
2025
:::tip
2026
-
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required option"** and click **OK** to proceed.
2026
+
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required"** option and click **OK** to proceed.
2027
2027
:::
2028
2028
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
2029
2029
@@ -2034,7 +2034,7 @@ The following commands are useful for managing and troubleshooting .NET installa
2034
2034
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
2035
2035
* Right-click on each entry and select **Uninstall**.
2036
2036
:::tip
2037
-
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required option"** and click **OK** to proceed.
2037
+
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required"** option and click **OK** to proceed.
2038
2038
:::
2039
2039
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
0 commit comments