From 3487778f9ccdfad9477bbbc58c685b1aad3399f3 Mon Sep 17 00:00:00 2001 From: Felicity Chapman Date: Fri, 11 Feb 2022 19:45:46 +0000 Subject: [PATCH] Fix broken links in today's broken link report (#25264) --- .../exporting-migration-data-from-your-enterprise.md | 2 +- .../preparing-to-migrate-data-to-your-enterprise.md | 6 +++--- .../about-githubs-ip-addresses.md | 2 +- .../security-best-practices-for-apps.md | 2 +- lib/excluded-links.js | 1 - 5 files changed, 6 insertions(+), 7 deletions(-) diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md index f3d8b48da6..689660934f 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md @@ -98,7 +98,7 @@ shortTitle: Export from your enterprise > logout > Connection to hostname closed. ``` -9. Copy the migration archive to your computer using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: +9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: ```shell $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop ``` diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md index 12b0ae88e1..177d878409 100644 --- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md +++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md @@ -19,7 +19,7 @@ shortTitle: Prepare to migrate data --- ## Preparing the migrated data for import to {% data variables.product.prodname_ghe_server %} -1. Using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target: +1. Using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy the migration archive generated from your source instance or organization to your {% data variables.product.prodname_ghe_server %} target: ```shell $ scp -P 122 /path/to/archive/MIGRATION_GUID.tar.gz admin@hostname:/home/admin/ @@ -43,7 +43,7 @@ shortTitle: Prepare to migrate data $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv ``` - If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)". -2. If there are conflicts, using the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer: +2. If there are conflicts, using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer: ```shell $ scp -P 122 admin@hostname:conflicts.csv ~/Desktop ``` @@ -133,7 +133,7 @@ The same process can be used to create mappings for each record that supports cu ### Applying modified migration data -1. After making changes, use the [`scp`](https://linuxacademy.com/blog/linux/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance: +1. After making changes, use the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command to apply your modified *conflicts.csv* (or any other mapping *.csv* file in the correct format) to the target instance: ```shell $ scp -P 122 ~/Desktop/conflicts.csv admin@hostname:/home/admin/ diff --git a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md index 480901f678..858faf9151 100644 --- a/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md +++ b/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md @@ -29,7 +29,7 @@ You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP add These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds. -These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges. +These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: [CIDR to IPv4 conversion site](https://www.ipaddressguide.com/cidr). We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API. diff --git a/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index edf1015910..a23805bf67 100644 --- a/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -60,4 +60,4 @@ For an example of an incident response workflow, see the "Data Breach Response P You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)." diff --git a/lib/excluded-links.js b/lib/excluded-links.js index 3452045cac..44ed1073e7 100644 --- a/lib/excluded-links.js +++ b/lib/excluded-links.js @@ -31,5 +31,4 @@ export default [ 'https://www.vmware.com/products/esxi-and-esx.html', 'https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5', 'https://wiki.oasis-open.org/security', - 'https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/', ]