Reword unprotected file repositories - #5089
Open
maximiliankolb wants to merge 1 commit into
Open
Conversation
If a file repository is unprotected, anyone that can connect to Foreman+Katello can download files via curl. If a file repository is protected, you need a valid debug certificate or entitlement. Protected/unprotected does not relate to transport security/HTTP vs HTTPS. Refs PR theforeman#5056
github-actions
Bot
added
Needs tech review
|
The PR preview for 579cab4 is available at theforeman-foreman-documentation-preview-pr-5089.surge.sh The following output files are affected by this PR: |
aneta-petrova
approved these changes
Jul 21, 2026
aneta-petrova
added
style review done
Contributor
Author
|
@jeremylenz Can you please do a tech review? |
jeremylenz
reviewed
Jul 22, 2026
jeremylenz
left a comment
jeremylenz
left a comment
Contributor
There was a problem hiding this comment.
This doesn't seem correct to me, but tagging @sjha4 and @ianballou to clarify.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changes are you introducing?
If a file repository is unprotected, anyone that can connect to Foreman+Katello can download files via curl.
If a file repository is protected, you need a valid debug certificate or entitlement.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Protected/unprotected does not relate to transport security/HTTP vs HTTPS.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Refs PR #5056
Tested on Foreman 3.18/Katello 4.20 with a self-signed certificate.
wgetalways redirected me fromhttp://foreman.example.com/...tohttps://foreman.example.com/.... -> I could not access the file over plain HTTP due to HSTS:URL transformed to HTTPS due to an HSTS policy.I also did not try to use a debug certificate/entitlement; I just tested that you cannot access it without:
403: [('PEM routines', '', 'no start line')].Contributor checklists
Please cherry-pick my commits into: