From 235bd86af37c6b5be5aa404ac4228051273f50cb Mon Sep 17 00:00:00 2001 From: Expo on server Date: Sun, 9 Oct 2022 00:32:26 +0100 Subject: [PATCH] ./pre-run.sh does not fixup git work --- security-warnings.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security-warnings.txt b/security-warnings.txt index c9c248e..236f7c9 100644 --- a/security-warnings.txt +++ b/security-warnings.txt @@ -1,8 +1,8 @@ System check identified some issues: WARNINGS: +?: (admin.W411) 'django.template.context_processors.request' must be enabled in DjangoTemplates (TEMPLATES) in order to use the admin navigation sidebar. ?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_BROWSER_XSS_FILTER, SECURE_REFERRER_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 SECRET_KEY, 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.