From: Steve Dickson <steved@redhat.com>
To: Petr Vorel <pvorel@suse.cz>, linux-nfs@vger.kernel.org
Cc: libtirpc-devel@lists.sourceforge.net,
Josue Ortega <josue@debian.org>, NeilBrown <neilb@suse.de>,
Thomas Blume <Thomas.Blume@suse.com>,
Yann Leprince <yann.leprince@ylep.fr>
Subject: Re: [PATCH rpcbind 0/4] Update systemd/rpcbind.service.in
Date: Sat, 31 Aug 2024 13:56:25 -0400 [thread overview]
Message-ID: <09fc607e-9d48-4fc6-91df-0fe31a3a6164@redhat.com> (raw)
In-Reply-To: <20240823002322.1203466-1-pvorel@suse.cz>
On 8/22/24 8:23 PM, Petr Vorel wrote:
> Hi,
>
> NOTE I'm not systemd expert, others may understand more.
>
> But trying to upstream various hardenings options which we have been
> using since 2021. Adding EnvironmentFile I tested locally today.
> systemd-tmpfiles-setup.service should be also safe.
>
> Kind regards,
> Petr
>
> Josue Ortega (1):
> man/rpcbind: Add Files section to manpage
>
> Petr Vorel (3):
> systemd/rpcbind.service.in: Add few default EnvironmentFile
> systemd/rpcbind.service.in: Add various hardenings options
> systemd/rpcbind.service.in: Want/After systemd-tmpfiles-setup
>
> man/rpcbind.8 | 8 ++++++++
> systemd/rpcbind.service.in | 16 +++++++++++++++-
> 2 files changed, 23 insertions(+), 1 deletion(-)
>
Committed... (tag: rpcbind-1_2_8-rc1)
steved.
prev parent reply other threads:[~2024-08-31 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 0:23 [PATCH rpcbind 0/4] Update systemd/rpcbind.service.in Petr Vorel
2024-08-23 0:23 ` [PATCH rpcbind 1/4] systemd/rpcbind.service.in: Add few default EnvironmentFile Petr Vorel
2024-08-23 0:23 ` [PATCH rpcbind 2/4] man/rpcbind: Add Files section to manpage Petr Vorel
2024-08-23 0:23 ` [RFC][PATCH rpcbind 3/4] systemd/rpcbind.service.in: Add various hardenings options Petr Vorel
2024-08-23 0:23 ` [RFC][PATCH rpcbind 4/4] systemd/rpcbind.service.in: Want/After systemd-tmpfiles-setup Petr Vorel
2024-08-23 1:01 ` Petr Vorel
2024-08-30 15:40 ` Steve Dickson
2024-08-30 16:51 ` Petr Vorel
2024-08-31 17:56 ` Steve Dickson [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=09fc607e-9d48-4fc6-91df-0fe31a3a6164@redhat.com \
--to=steved@redhat.com \
--cc=Thomas.Blume@suse.com \
--cc=josue@debian.org \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pvorel@suse.cz \
--cc=yann.leprince@ylep.fr \
/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;
as well as URLs for NNTP newsgroup(s).