summaryrefslogtreecommitdiffstats
path: root/security-warnings.txt
diff options
context:
space:
mode:
authorPhilip Sargent <philip.sargent@klebos.com>2021-03-31 21:51:17 +0100
committerPhilip Sargent <philip.sargent@klebos.com>2021-03-31 21:51:17 +0100
commit7cccf4daf15f16f3b7b4dc7909862fc2839caf4f (patch)
treec7d01dc580db7d1ce7adce46b3ee172ae645558a /security-warnings.txt
parente1cf43c260c75b3e047d02c49d8e26b2bb14e153 (diff)
downloadtroggle-7cccf4daf15f16f3b7b4dc7909862fc2839caf4f.tar.gz
troggle-7cccf4daf15f16f3b7b4dc7909862fc2839caf4f.tar.bz2
troggle-7cccf4daf15f16f3b7b4dc7909862fc2839caf4f.zip
move *_views files to /views/*
Diffstat (limited to 'security-warnings.txt')
-rw-r--r--security-warnings.txt8
1 files changed, 2 insertions, 6 deletions
diff --git a/security-warnings.txt b/security-warnings.txt
index ee3c723..4b489c0 100644
--- a/security-warnings.txt
+++ b/security-warnings.txt
@@ -1,14 +1,10 @@
System check identified some issues:
WARNINGS:
-?: (security.W004) You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.
-
-?: (security.W008) Your SECURE_SSL_REDIRECT setting is not set to True. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting True or configure a load balancer or reverse-proxy server to redirect all connections to HTTPS.
-
+?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE_CLASSES so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_BROWSER_XSS_FILTER, and SECURE_SSL_REDIRECT settings will have no effect.
?: (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_CLASSES, 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.
-
?: (security.W019) You have 'django.middleware.clickjacking.XFrameOptionsMiddleware' in your MIDDLEWARE_CLASSES, but X_FRAME_OPTIONS is not set to 'DENY'. The default is 'SAMEORIGIN', but unless there is a good reason for your site to serve other parts of itself in a frame, you should change it to 'DENY'.
System check identified 5 issues (0 silenced).