Update security model to clarify Connection Editing user's capabilities #37688
Conversation
This file contains 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
While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted.
Taragolis
approved these changes
Feb 25, 2024
eladkal
approved these changes
Feb 25, 2024
abhishekbhakat
pushed a commit
to abhishekbhakat/my_airflow
that referenced
this pull request
Mar 5, 2024
…es (apache#37688) While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted.
ephraimbuddy
pushed a commit
that referenced
this pull request
Mar 6, 2024
…es (#37688) While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted. (cherry picked from commit 8658c22)
ephraimbuddy
pushed a commit
that referenced
this pull request
Mar 6, 2024
…es (#37688) While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted. (cherry picked from commit 8658c22)
utkarsharma2
pushed a commit
to astronomer/airflow
that referenced
this pull request
Apr 22, 2024
…es (apache#37688) While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While we already mentioned and explained in a number of places that connection editing is dangeerous, we should explicitly menion that misconfiguring of connections might lead to RCE situations and that this is not preventable - and that connection editing users should be highly trusted.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.