From: 7ppKb5bW <pONy4THS@protonmail.com>
To: "passt-dev@passt.top" <passt-dev@passt.top>
Subject: Re: [PATCH] pasta.te: fix demo.sh and remove one duplicate rule
Date: Sat, 01 Mar 2025 21:48:53 [thread overview]
Message-ID: <ggrgrY5P8dN27EG2XH5ZRZusen99hHDlZg6-YvaHp1ozrr2HQHuAr9ilrVRjbti6j6gfE6Q3Y3vTUGoI0GZH7xjlw-k5PVbL9dPacKxBMqA=@protonmail.com> (raw)
In-Reply-To: <BD40k8OG-5BpMWJgJn-GLY9qNZqrSUJCl3S0x2c_1cnn4DUl6azPh8w_Iiw6lIcT0BjV1T61XTalZM9rDhMT50kntShD8Jfcnj6AFjyHMuM=@protonmail.com>
> ---
> contrib/selinux/pasta.te | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/contrib/selinux/pasta.te b/contrib/selinux/pasta.te
> index 69be081..d0ff0cc 100644
> --- a/contrib/selinux/pasta.te
> +++ b/contrib/selinux/pasta.te
> @@ -171,7 +171,7 @@ allow pasta_t init_t:lnk_file read;
> allow pasta_t init_t:unix_stream_socket connectto;
> allow pasta_t init_t:dbus send_msg;
> allow pasta_t init_t:system status;
> -allow pasta_t unconfined_t:dir search;
> +allow pasta_t unconfined_t:dir { read search };
> allow pasta_t unconfined_t:file read;
> allow pasta_t unconfined_t:lnk_file read;
> allow pasta_t self:process { setpgid setcap };
> @@ -192,8 +192,6 @@ allow pasta_t sysctl_net_t:dir search;
> allow pasta_t sysctl_net_t:file { open read write };
> allow pasta_t kernel_t:system module_request;
>
> -allow pasta_t nsfs_t:file read;
> -
> allow pasta_t proc_t:dir mounton;
> allow pasta_t proc_t:filesystem mount;
> allow pasta_t net_conf_t:lnk_file read;
> --
Sorry, it should be " allow pasta_t unconfined_t:dir { open read search }; "
prev parent reply other threads:[~2025-03-01 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 19:21 [PATCH] pasta.te: fix demo.sh and remove one duplicate rule 7ppKb5bW
2025-02-03 6:40 ` Stefano Brivio
2025-03-01 20:48 ` 7ppKb5bW [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='ggrgrY5P8dN27EG2XH5ZRZusen99hHDlZg6-YvaHp1ozrr2HQHuAr9ilrVRjbti6j6gfE6Q3Y3vTUGoI0GZH7xjlw-k5PVbL9dPacKxBMqA=@protonmail.com' \
--to=pony4ths@protonmail.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).