From: theflamefire89@gmail.com
To: cip-dev@lists.cip-project.org
Subject: [4.4.y] cred_getsecid hook
Date: Thu, 16 Jun 2022 06:30:50 -0700 [thread overview]
Message-ID: <PVAj.1655386250477927031.ATkI@lists.cip-project.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
While working on backporting the fix for CVE-2021-39686 in the Android-"version" of the 4.4.y kernel I noticed the missing cred_getsecid hook introduced in e.g. 4.19.y by 3ec30113264a7bcd389f51d1738e42da0f41bb5a ( https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-4.19.y&id=3ec30113264a7bcd389f51d1738e42da0f41bb5a )
It seems the LSM security_* hooks haven't received updates for a while in this kernel. E.g. a source of error due to missed list HEAD init is due to 0302e28dee643932ee7b3c112ebccdbb9f8ec32c ( https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-4.19.y&id=0302e28dee643932ee7b3c112ebccdbb9f8ec32c ) merging in 3dfc9b02864b19f4dab376f14479ee4ad1de6c9e ( https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/security/security.c?h=linux-4.19.y&id=3dfc9b02864b19f4dab376f14479ee4ad1de6c9e ) which makes the HEAD initialization shorter and more reliable but trying to get that commit in results in quite a bit of merge conflicts as hooks have been added/removed in 4.19 which is not yet in 4.4.
Anyway: Are there any plans to synchronize the hooks in 4.4 with those in more recent kernels?
Regards,
Alexander
[-- Attachment #2: Type: text/html, Size: 1382 bytes --]
next reply other threads:[~2022-06-16 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:30 theflamefire89 [this message]
2022-06-22 12:06 ` [cip-dev] [4.4.y] cred_getsecid hook Pavel Machek
2022-06-29 15:44 ` theflamefire89
2022-06-29 18:27 ` [cip-dev] " Pavel Machek
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=PVAj.1655386250477927031.ATkI@lists.cip-project.org \
--to=theflamefire89@gmail.com \
--cc=cip-dev@lists.cip-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.