Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Thu, 19 Dec 2024 11:53:32 +0000
Message-Id: <D6FNNBC17CRS.WG0RAAG9WKMH@posteo.net>
Subject: Re: Persisting apparmor between kernel upgrades with syslinux
From: "Sertonix" <sertonix@posteo.net>
To: "revsuine" <pid1@revsuine.xyz>, <~alpine/users@lists.alpinelinux.org>
References: <e9db0edf3665cb88d2b33d970b1bea67af815e5f.camel@revsuine.xyz>
In-Reply-To: <e9db0edf3665cb88d2b33d970b1bea67af815e5f.camel@revsuine.xyz>

> Hi there,
>
> I've been using AppArmor using SYSLINUX according to the wiki:
> https://wiki.alpinelinux.org/wiki/AppArmor#With_SYSLINUX
>
> However, /boot/extlinux.conf gets overwritten every time the kernel updat=
es,
> meaning I have to manually repeat the steps of the wiki article in order =
for
> AppArmor to remain enabled after a kernel update.
>
> Does anyone have suggestions on the best way to keep AppArmor enabled eve=
n with
> kernel updates?

When using the update trigger you need to edit 'default_kernel_opts' in
/etc/update-extlinux.conf to something like this:

default_kernel_opts=3D"quiet lsm=3Dlandlock,yama,apparmor"

> Thanks.