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.
@@ -414,7 +414,7 @@ sh install-python-els-repo.sh --license-key XXX-XXXXXXXXXXXX
414
414
```
415
415
3. Verify that the installation was successful.
416
416
417
-
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.
417
+
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.
418
418
```
419
419
yum info python2
420
420
@@ -436,7 +436,7 @@ Description : Python 2 is an old version of the language that is incompatible
436
436
```
437
437
yum install python2 --enablerepo crb
438
438
```
439
-
Once installed, you can use python2 in the usual way.
439
+
5. Once installed, you can use python2 in the usual way.
440
440
```python
441
441
$ python2
442
442
Python 2.7.18 (default, Jun 30 2022, 00:00:00)
@@ -449,15 +449,15 @@ Hello, World!
449
449
### Installation instructions of a local mirror
450
450
451
451
We provide the ability to create local mirrors of Python for ELS updates.
452
-
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]).
452
+
*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]).
453
453
454
-
To create a local mirror of the repository with security updates via `rsync`, use the following:
454
+
*To create a local mirror of the repository with security updates via `rsync`, use the following:
455
455
456
456
```
457
457
rsync://repo.cloudlinux.com/PYTHON_ELS/
458
458
```
459
459
460
-
Example of creating a local mirror for all supported OS versions:
460
+
*Example of creating a local mirror for all supported OS versions:
@@ -508,7 +508,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
508
508
-**Low-severity CVEs:** Patches provided within 90 days
509
509
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
510
510
511
-
### **Incident Reporting and Response Timeframe**
511
+
### Incident Reporting and Response Timeframe
512
512
513
513
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.
514
514
@@ -548,7 +548,7 @@ You need username and password in order to use TuxCare ELS Spring repository. An
548
548
549
549
**Maven**
550
550
551
-
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:
551
+
*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:
552
552
553
553
```
554
554
<?xml version="1.0" encoding="UTF-8"?>
@@ -563,16 +563,16 @@ If you are using Maven as your build automation tool, you will need to make chan
563
563
</settings>
564
564
```
565
565
566
-
Set your credentials via the following enviromnent variables:
566
+
*Set your credentials via the following environment variables:
567
567
568
568
```
569
569
export USERNAME=your-username
570
570
export PASSWORD=your-password
571
571
```
572
572
573
-
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).
573
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
574
574
575
-
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:
575
+
*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:
576
576
577
577
```
578
578
<repositories>
@@ -583,11 +583,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
583
583
</repositories>
584
584
```
585
585
586
-
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.
586
+
*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.
587
587
588
588
**Gradle**
589
589
590
-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
590
+
*If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
591
591
592
592
```
593
593
repositories {
@@ -601,16 +601,16 @@ If you are using Gradle as your build automation tool, make sure to include the
601
601
}
602
602
```
603
603
604
-
Set your credentials via the following enviromnent variables:
604
+
*Set your credentials via the following environment variables:
605
605
606
606
```
607
607
export ORG_GRADLE_PROJECT_USERNAME=your-username
608
608
export ORG_GRADLE_PROJECT_PASSWORD=your-password
609
609
```
610
610
611
-
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).
611
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
612
612
613
-
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.
613
+
*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.
614
614
615
615
### Verification
616
616
@@ -1589,7 +1589,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
1589
1589
-**Low-severity CVEs:** Patches provided within 90 days
1590
1590
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
1591
1591
1592
-
### **Incident Reporting and Response Timeframe**
1592
+
### Incident Reporting and Response Timeframe
1593
1593
1594
1594
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.
1595
1595
@@ -1621,13 +1621,13 @@ This guide outlines the steps needed to integrate the TuxCare ELS for Apache Tom
1621
1621
### Steps
1622
1622
1623
1623
### Step 1: Get user credentials
1624
-
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]
1624
+
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]).
1625
1625
1626
1626
### Step 2: Create or Modify Your Build Tool Settings
1627
1627
1628
1628
**Maven**
1629
1629
1630
-
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:
1630
+
*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:
1631
1631
1632
1632
```
1633
1633
<?xml version="1.0" encoding="UTF-8"?>
@@ -1642,16 +1642,16 @@ If you are using Maven as your build automation tool, you will need to make chan
1642
1642
</settings>
1643
1643
```
1644
1644
1645
-
Set your credentials via the following enviromnent variables:
1645
+
*Set your credentials via the following environment variables:
1646
1646
1647
1647
```
1648
1648
export USERNAME=your-username
1649
1649
export PASSWORD=your-password
1650
1650
```
1651
1651
1652
-
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).
1652
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
1653
1653
1654
-
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:
1654
+
*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:
1655
1655
1656
1656
```
1657
1657
<repositories>
@@ -1662,11 +1662,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
1662
1662
</repositories>
1663
1663
```
1664
1664
1665
-
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.
1665
+
*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.
1666
1666
1667
1667
**Gradle**
1668
1668
1669
-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
1669
+
*If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
1670
1670
1671
1671
```
1672
1672
repositories {
@@ -1680,16 +1680,16 @@ If you are using Gradle as your build automation tool, make sure to include the
1680
1680
}
1681
1681
```
1682
1682
1683
-
Set your credentials via the following enviromnent variables:
1683
+
*Set your credentials via the following environment variables:
1684
1684
1685
1685
```
1686
1686
export ORG_GRADLE_PROJECT_USERNAME=your-username
1687
1687
export ORG_GRADLE_PROJECT_PASSWORD=your-password
1688
1688
```
1689
1689
1690
-
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).
1690
+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
1691
1691
1692
-
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.
1692
+
*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.
1693
1693
1694
1694
### Verification
1695
1695
@@ -1934,7 +1934,7 @@ The following commands are useful for managing and troubleshooting .NET installa
1934
1934
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
1935
1935
* Click on each entry and select **Uninstall**.
1936
1936
:::tip
1937
-
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.
1937
+
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.
1938
1938
:::
1939
1939
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
1940
1940
@@ -1945,7 +1945,7 @@ The following commands are useful for managing and troubleshooting .NET installa
1945
1945
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
1946
1946
* Right-click on each entry and select **Uninstall**.
1947
1947
:::tip
1948
-
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.
1948
+
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.
1949
1949
:::
1950
1950
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
0 commit comments