From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/4] build: Always define confdir and statedir
Date: Tue, 01 Feb 2022 10:32:52 +0100 [thread overview]
Message-ID: <de2e9b1426587214fcb1b28bb3bec265fd8f9044.camel@hadess.net> (raw)
In-Reply-To: <61d3fea272805d6bfb1a6cf5883404ea7e294e7c.camel@hadess.net>
On Wed, 2022-01-26 at 14:45 +0100, Bastien Nocera wrote:
> This change specifically? Check the next patches in the series, and
> you'll see pretty quickly.
>
> For the rest of the patchset, check this man page for details on each
> of the directives:
> https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Security
>
> There's a fair amount of other directives we could use on top of
> those
> ones, but we can add them iteratively (and it makes bisecting easier,
> in case we forget about a particular use case).
Did you have any more questions about this patchset?
next prev parent reply other threads:[~2022-02-01 9:32 UTC|newest]
Thread overview: 13+ 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 ` [PATCH 4/4] systemd: More lockdown Bastien Nocera
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 [this message]
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-11-24 14:15 ` 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=de2e9b1426587214fcb1b28bb3bec265fd8f9044.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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