Changes between Version 4 and Version 5 of SecurityTeam


Ignore:
Timestamp:
Mar 3, 2025, 10:07:21 AM (7 hours ago)
Author:
Natalia Bidart
Comment:

Added a few more response templates.

Legend:

Unmodified
Added
Removed
Modified
  • SecurityTeam

    v4 v5  
    55== Canned Responses ==
    66
    7 
    87=== Report acknowledgement ===
    98
    10 Hi,
     9Hello,
    1110
    12 Thank you for the report!
     11Thank you for your report. We will investigate and get back to you soon. In the meantime, please keep this information confidential.
    1312
    14 We will investigate and get back to you soon.
    15 
    16 Please keep this private until we complete our analysis.
     13If you haven't already, please review how the Django security team evaluates reports: https://docs.djangoproject.com/en/dev/internals/security/.
    1714
    1815Note that it can take several weeks before we have completed our analysis. There is no need to chase the security team unless you discover new, relevant information. All reports aim to be resolved within the industry-standard 90 days.
    1916
    20 === Confirmation of vulnerability ===
     17Kind regards, the Django Security Team.
     18
     19=== DMARC/SPF/Email Spoofing ===
     20
     21Hello,
     22
     23Thank you for your report. The current DMARC and SPF settings are intentional, and we do not consider this a vulnerability.
     24
     25For more information on how the Django security team evaluates reports, please see: https://docs.djangoproject.com/en/dev/internals/security/.
     26
     27Kind regards, the Django Security Team.
     28
     29=== Report about djangoproject.com ===
     30
     31Hello,
     32
     33Thank you for your report. This mailing list is intended for reporting security issues related to the Django web framework, rather than its website. I will forward your concern to our Ops team, but you can consider this issue closed.
     34
     35For more information on how the Django security team evaluates reports, please see: https://docs.djangoproject.com/en/dev/internals/security/.
     36
     37Kind regards, the Django Security Team.
     38
     39=== Asked for support instead ===
     40
     41Hello,
     42
     43This mailing list is intended for reporting security issues in the Django web framework, not for support related to using or contributing to Django.
     44
     45For assistance, please refer to the Getting Help page (https://docs.djangoproject.com/en/dev/faq/help/), where you'll find resources and communities ready to support you. Following these guidelines will also help you structure your question in a way that makes it easier for others to assist.
     46
     47Thanks for your understanding!
     48
     49== Confirmation of vulnerability ==
    2150
    2251Hello {{ name }},
Back to Top