potiuk opened a new pull request, #32098:
URL: https://github.com/apache/airflow/pull/32098

   This change updates the security model of Airflow to better explain what are 
the capabilities of various kinds of users in Airflow deployments and give both 
users and security researchers a way to understand what security measures they 
can take and whether they can qualify potential security issues in Airflow 
properly - taking into account that various users of Airflow have various 
capabilities and behaviours considered by some of the users as security 
vulnerabilities, are standard capabilities of the users.
   
   It also splits the security information of ours in two separate pages:
   
   * .github/SECURITY.md where we explain how to report the issues to Apache 
Airflow security team by the researchers
   
   * documentation security/index.html which is available via Airflow Website 
where we explain what our security model is and the different kinds of users we 
have.
   
   Both serve slightly different purpose and both contain cross-reference links 
to each other in order to be able to redirect people who read about the 
security model to find out how they can report the issues but also to guide 
security researchers who want to assess whether their findings are real 
vulnerabilities, or rather normal behaviours following the Airflow Security 
model.
   
   Security has been also moved to be a top level topic, so that it is easier 
to find and navigate to. Old links have been redirected to the new locations.
   
   Also chapters were added explaining Airflow vs. Providers security releases, 
what is the relation between Airflow and Providers security issues and how 
users should treat security announcements in providers.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to