Hi Linus,
Can you please pull the following bug fixes for apparmor
Thanks!
- John
The following changes since commit b8a5afa418c1f5c8d7814ef829a88e60ae52f618:
net: correct zerocopy refcnt with udp MSG_MORE (2019-05-31 06:40:10 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2019-06-06
for you to fetch changes up to dd60c38193b1cd8bc1cbde1425881cd5227ef466:
apparmor: enforce nullbyte at end of tag string (2019-05-31 06:50:00 -0700)
----------------------------------------------------------------
+ Bug Fixes
- Fix PROFILE_MEDIATES for untrusted input
- enforce nullbyte at end of tag string
----------------------------------------------------------------
Jann Horn (1):
apparmor: enforce nullbyte at end of tag string
John Johansen (1):
apparmor: fix PROFILE_MEDIATES for untrusted input
security/apparmor/include/policy.h | 11 ++++++++++-
security/apparmor/policy_unpack.c | 2 +-
2 files changed, 11 insertions(+), 2 deletions(-)
On Thu, Jun 6, 2019 at 5:39 PM John Johansen
<[email protected]> wrote:
>
> Can you please pull the following bug fixes for apparmor
No I can not.
You have for some completely unrecognizable reason rebased OTHER PEOPLES WORK.
There are two new apparmor commits in there, but there are also 89
random rebased patches from the networking tree.
What is going with all the security subsystem issues? Why does this
garbage keep on happening, and why are the security trees doing this
when everybody else has learnt.
DO NOT REBASE. NOT EVER. YOU CLEARLY DO NOT KNOW WHAT YOU ARE DOING.
"git rebase" and "git merge" are not commands you should ever EVER
EVER use, because you don't seem to understand what they do.
I'm seriously fed up with all the security subsystem by now. This is
not ok. It's not even one person, it seems to be a common issue where
people do completely odd things that make zero sense.
Linus