On Mon, Nov 15, 2021 at 08:04:05PM +0100, Ondrej Mosnacek wrote:
> On Mon, Nov 15, 2021 at 7:14 PM Alistair Delva <adelva@xxxxxxxxxx> wrote:
> > Booting to Android userspace on 5.14 or newer triggers the following
> > SELinux denial:
> >
> > avc: denied { sys_nice } for comm="init" capability=23
> > scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability
> > permissive=0
> >
> > Init is PID 0 running as root, so it already has CAP_SYS_ADMIN. For
> > better compatibility with older SEPolicy, check ADMIN before NICE.
>
> But with this patch you in turn punish the new/better policies that
> try to avoid giving domains CAP_SYS_ADMIN unless necessary (using only
> the more granular capabilities wherever possible), which may now get a
> bogus sys_admin denial. IMHO the order is better as it is, as it
> motivates the "good" policy writing behavior - i.e. spelling out the
> capability permissions more explicitly and avoiding CAP_SYS_ADMIN.
>
> IOW, if you domain does CAP_SYS_NICE things, and you didn't explicitly
> grant it that (and instead rely on the CAP_SYS_ADMIN fallback), then
> the denial correctly flags it as an issue in your policy and
> encourages you to add that sys_nice permission to the domain. Then
> when one beautiful hypothetical day the CAP_SYS_ADMIN fallback is
> removed, your policy will be ready for that and things will keep
> working.
>
> Feel free to carry that patch downstream if patching the kernel is
> easier for you than fixing the policy, but for the upstream kernel
> this is just a step in the wrong direction.
So you want to "punish" existing systems by throwing up a warning where
there used to not be one? That is not nice, you need to handle
upgrading kernels without breaking or causing problems like this.
Yes, SELinux has done this in the past, with many different things, but
that does not mean that it _should_ do this. Please realize that you do
not want to punish people from upgrading their kernel to a newer
version. If you do so, they will never upgrade.
thanks,
greg k-h
