From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 4/4] systemd: More lockdown
Date: Wed, 26 Jan 2022 12:36:38 +0100 [thread overview]
Message-ID: <20220126113638.1706785-4-hadess@hadess.net> (raw)
In-Reply-To: <20220126113638.1706785-1-hadess@hadess.net>
bluetoothd does not need to execute mapped memory, or real-time
access, so block those.
---
src/bluetooth.service.in | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/bluetooth.service.in b/src/bluetooth.service.in
index 4daedef2a..f18801866 100644
--- a/src/bluetooth.service.in
+++ b/src/bluetooth.service.in
@@ -22,9 +22,15 @@ ProtectControlGroups=true
ReadWritePaths=@statedir@
ReadOnlyPaths=@confdir@
+# Execute Mappings
+MemoryDenyWriteExecute=true
+
# Privilege escalation
NoNewPrivileges=true
+# Real-time
+RestrictRealtime=true
+
[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service
--
2.34.1
next prev parent reply other threads:[~2022-01-26 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:36 [PATCH 1/4] build: Always define confdir and statedir Bastien Nocera
2022-01-26 11:36 ` [PATCH 2/4] systemd: Add PrivateTmp and NoNewPrivileges options Bastien Nocera
2022-01-26 11:36 ` [PATCH 3/4] systemd: Add more filesystem lockdown Bastien Nocera
2022-01-26 11:36 ` Bastien Nocera [this message]
2022-01-26 11:38 ` [PATCH 1/4] build: Always define confdir and statedir Bastien Nocera
2022-01-26 13:31 ` Marcel Holtmann
2022-01-26 13:45 ` Bastien Nocera
2022-02-01 9:32 ` Bastien Nocera
2022-04-12 19:48 ` Luiz Augusto von Dentz
2022-01-26 14:07 ` [1/4] " bluez.test.bot
2022-01-31 18:45 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2017-09-20 11:48 [PATCH 1/4] " Bastien Nocera
2017-09-20 11:48 ` [PATCH 4/4] systemd: More lockdown Bastien Nocera
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=20220126113638.1706785-4-hadess@hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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