From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 3/4] httpd: apply the same security headers on the captive portal instance as we do elsewhere
Date: Mon, 12 Apr 2021 23:01:13 +0200 [thread overview]
Message-ID: <5251bce1-49af-64e5-a858-5e33210d9e6b@ipfire.org> (raw)
In-Reply-To: <8698f06c-19c9-1680-f179-4d50c00bed1a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
The Captive Portal should not be framed or leak sensitive detail via
Referrers either.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/httpd/vhosts.d/captive.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/config/httpd/vhosts.d/captive.conf b/config/httpd/vhosts.d/captive.conf
index 629fa8180..51af6eac4 100644
--- a/config/httpd/vhosts.d/captive.conf
+++ b/config/httpd/vhosts.d/captive.conf
@@ -11,6 +11,8 @@ Listen 1013
Header always set X-Content-Type-Options nosniff
Header always set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'"
+ Header always set Referrer-Policy strict-origin
+ Header always set X-Frame-Options sameorigin
ScriptAlias /cgi-bin/ /srv/web/ipfire/cgi-bin/captive/
Alias /assets/ /srv/web/ipfire/html/captive/assets/
--
2.26.2
next prev parent reply other threads:[~2021-04-12 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 21:00 [PATCH 1/4] httpd: remove compatibility instructions for very old browsers Peter Müller
2021-04-12 21:00 ` [PATCH 2/4] httpd: disable sending ETag header completely Peter Müller
2021-04-12 21:01 ` Peter Müller [this message]
2021-04-12 21:01 ` [PATCH 4/4] httpd: delete comment blocks and unused directives from our configuration Peter Müller
2021-04-14 17:24 ` [PATCH 1/4] httpd: remove compatibility instructions for very old browsers Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5251bce1-49af-64e5-a858-5e33210d9e6b@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox