Update repository URLs to use HTTPS #511
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR addresses the usage of HTTP for repository URLs in the script. Currently, the script uses HTTP for fetching packages from Ubuntu repositories, and i'm uncertain whether this choice was intentional.
Changes
repo_setupfunction.Motivation and Context
The primary motivation for this change is to improve security by migrating to HTTPS, which ensures that all communication with the repository is encrypted. This is especially important for protecting the integrity and authenticity of the packages being downloaded.
Although HTTP still works, it lacks the encryption layer provided by HTTPS, which makes it vulnerable to interception and tampering. Migrating to HTTPS ensures that the system is protected from these security risks.
Additionally, some air-gapped environments or highly restricted networks may block outbound HTTP traffic on port 80, which could prevent the script from successfully fetching packages. In such cases, using HTTPS (typically over port 443) is often the only available option to access external repositories. Migrating to HTTPS ensures compatibility with these environments.
If maintaining HTTP support is still desired, I can modify the script to offer the option to use either HTTP or HTTPS, based on user preference.