airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3431) Document how to report security vulnerabilities and issues safely
Date Mon, 03 Dec 2018 10:02:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706919#comment-16706919
] 

ASF GitHub Bot commented on AIRFLOW-3431:
-----------------------------------------

ashb closed pull request #4262: [AIRFLOW-3431] Document how to report security vulnerabilities.
URL: https://github.com/apache/incubator-airflow/pull/4262
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/security.rst b/docs/security.rst
index 1adefcd834..de62deb1e6 100644
--- a/docs/security.rst
+++ b/docs/security.rst
@@ -34,6 +34,27 @@ Be sure to checkout :doc:`api` for securing the API.
    environment variables) as ``%%``, otherwise Airflow might leak these
    passwords on a config parser exception to a log.
 
+Reporting Vulnerabilities
+-------------------------
+
+The Apache Software Foundation takes security issues very seriously. Apache
+Airflow specifically offers security features and is responsive to issues
+around its features. If you have any concern around Airflow Security or believe
+you have uncovered a vulnerability, we suggest that you get in touch via the
+e-mail address security@apache.org. In the message, try to provide a
+description of the issue and ideally a way of reproducing it. The security team
+will get back to you after assessing the description.
+
+Note that this security address should be used only for undisclosed
+vulnerabilities. Dealing with fixed issues or general questions on how to use
+the security features should be handled regularly via the user and the dev
+lists. Please report any security problems to the project security address
+before disclosing it publicly.
+
+The `ASF Security team's page <https://www.apache.org/security/>`_ describes
+how vulnerability reports are handled, and includes PGP keys if you wish to use
+that.
+
 Web Authentication
 ------------------
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Document how to report security vulnerabilities and issues safely
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-3431
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3431
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Ash Berlin-Taylor
>            Assignee: Ash Berlin-Taylor
>            Priority: Major
>
> Add to our docs how poeple can report security vulnerabilities in Airflow safely and
responsibly. Point QU30 in the maturity docs:
> {quote}The project provides a well-documented channel to report security issues, along
with a documented way of responding to them.\{quote}
> We will follow the Apache way and use [security@apache.org|mailto:security@apache.org]
for now, but we need to say this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message