From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: apparmor: load profiles in parallel
Date: Sun, 14 Feb 2021 23:10:51 +0100 [thread overview]
Message-ID: <20210214221051.S57fBEbAvkoJEo4NO4pAUdOh2UbvBRAI0lekmQx_8IY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28766@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/28766#issuecomment-778850010
Comment:
Upstream has optimized code to do this (`/usr/lib/apparmor/rc.apparmor.functions` `parse_profiles()`).
Currently we fudge it up with our custom one-by-one loading. Now we are reimplementing?
Can we deprecate the runit "complain" mode and direct users to the `aa-complain(8)` utility? It would bring us closer to upstream and other distros.
Minimal example of what using the upstream provided code would look like (they make you define log functions):
```
set -e
test -d /sys/kernel/security/apparmor
AA_FUNCTIONS=/usr/lib/apparmor/rc.apparmor.functions
test -r "$AA_FUNCTIONS"
aa_action() { :; }
aa_log_warning_msg() { :; }
aa_log_failure_msg() { :; }
aa_log_action_start() { :; }
aa_log_action_end() { :; }
aa_log_daemon_msg() { :; }
aa_log_skipped_msg() { :; }
aa_log_end_msg() { :; }
set +e
. "$AA_FUNCTIONS"
apparmor_restart
exit $?
```
next prev parent reply other threads:[~2021-02-14 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 21:41 [PR PATCH] " thypon
2021-02-14 21:44 ` [PR PATCH] [Updated] " thypon
2021-02-14 21:49 ` [PR REVIEW] " ericonr
2021-02-14 21:51 ` thypon
2021-02-14 21:54 ` [PR PATCH] [Updated] " thypon
2021-02-14 21:58 ` [PR REVIEW] " Gottox
2021-02-14 22:10 ` CameronNemo [this message]
2021-02-14 22:28 ` thypon
2021-02-14 22:29 ` thypon
2021-02-14 22:31 ` Duncaen
2021-02-14 22:38 ` Duncaen
2021-02-14 22:38 ` Duncaen
2021-02-14 23:05 ` [PR PATCH] [Updated] " thypon
2021-02-14 23:06 ` thypon
2021-02-14 23:19 ` [PR PATCH] [Updated] " thypon
2021-02-14 23:21 ` thypon
2021-02-15 22:52 ` [PR PATCH] [Merged]: " thypon
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=20210214221051.S57fBEbAvkoJEo4NO4pAUdOh2UbvBRAI0lekmQx_8IY@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).