From: patchwork-bot+bluetooth@kernel.org
To: Antonio Russo <aerusso@aerusso.net>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
kernel.org@pileofstuff.org, luiz.von.dentz@intel.com,
carnil@debian.org, agx@sigxcpu.org
Subject: Re: [PATCH] Do not start mpris-proxy for system users
Date: Tue, 03 Jun 2025 17:30:31 +0000 [thread overview]
Message-ID: <174897183199.1598265.1883181146579603180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9d7984b8-79c6-478e-95c8-28a6d4a7ba9b@aerusso.net>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 2 Jun 2025 21:37:20 -0600 you wrote:
> A default installation of bluez results in the systemd user unit
> mpris-proxy.service being started for all users---including root.
> This unnecessarily exposes system users to any security
> vulnerabilities in mpris-proxy.
>
> Inhibit this default behavior by using ConditionUser=!@system.
>
> [...]
Here is the summary with links:
- Do not start mpris-proxy for system users
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=99861c249c86
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-03 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 15:04 Do not start mpris-proxy for root user Antonio Russo
2025-05-17 13:12 ` Salvatore Bonaccorso
2025-05-17 14:06 ` Guido Günther
2025-05-18 13:12 ` Andrew Sayers
2025-05-31 8:20 ` Salvatore Bonaccorso
2025-05-31 18:17 ` Guido Günther
2025-06-02 0:29 ` Antonio Russo
2025-06-02 18:18 ` Luiz Augusto von Dentz
2025-06-03 3:37 ` [PATCH] Do not start mpris-proxy for system users Antonio Russo
2025-06-03 5:10 ` bluez.test.bot
2025-06-03 6:59 ` [PATCH] " Guido Günther
2025-06-03 7:16 ` Paul Menzel
2025-06-03 14:35 ` Andrew Sayers
2025-06-03 17:30 ` patchwork-bot+bluetooth [this message]
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=174897183199.1598265.1883181146579603180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aerusso@aerusso.net \
--cc=agx@sigxcpu.org \
--cc=carnil@debian.org \
--cc=kernel.org@pileofstuff.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
/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