summaryrefslogtreecommitdiffstats
path: root/security-warnings.txt
diff options
context:
space:
mode:
Diffstat (limited to 'security-warnings.txt')
-rw-r--r--security-warnings.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/security-warnings.txt b/security-warnings.txt
index 90aef32..a2802f0 100644
--- a/security-warnings.txt
+++ b/security-warnings.txt
@@ -1,10 +1,10 @@
+Reading inline script metadata from `manage.py`
System check identified some issues:
WARNINGS:
?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_REFERRER_POLICY, SECURE_CROSS_ORIGIN_OPENER_POLICY, and SECURE_SSL_REDIRECT settings will have no effect.
-?: (security.W009) Your SECRET_KEY has less than 50 characters, less than 5 unique characters, or it's prefixed with 'django-insecure-' indicating that it was generated automatically by Django. Please generate a long and random value, otherwise many of Django's security-critical features will be vulnerable to attack.
?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.
?: (security.W016) You have 'django.middleware.csrf.CsrfViewMiddleware' in your MIDDLEWARE, but you have not set CSRF_COOKIE_SECURE to True. Using a secure-only CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token.
?: (security.W018) You should not have DEBUG set to True in deployment.
-System check identified 5 issues (0 silenced).
+System check identified 4 issues (0 silenced).