From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org, Chris PeBenito <pebenito@ieee.org>
Subject: Re: [PATCH] certbot V2
Date: Tue, 15 Mar 2022 00:56:13 +1100 [thread overview]
Message-ID: <2933855.8EzMN8LN0u@xev> (raw)
In-Reply-To: <736887c7-d588-8562-4933-030947915fe2@ieee.org>
On Tuesday, 15 March 2022 00:53:14 AEDT Chris PeBenito wrote:
> > -logging_search_logs(certbot_t)
> > +logging_log_filetrans(certbot_t, certbot_log_t, dir, "letsencrypt")
>
> I don't see any conflicting type_transitions here or above. If there are
> none, then the letsencrypt should be removed.
Do we want to allow it to create whatever directories it likes under /var/log?
What if it decides to create something else inappropriately?
There aren't any conflicts, just an issue of whether we want to allow it
unrestricted write access to an important directory.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2022-03-14 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 5:19 [PATCH] certbot V2 Russell Coker
2022-03-14 13:53 ` Chris PeBenito
2022-03-14 13:56 ` Russell Coker [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=2933855.8EzMN8LN0u@xev \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--cc=selinux-refpolicy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).